Skip to content

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Jan 14, 2024

In #36003 we thought we changed default "version" image to point to "newest" python version not to the "oldest" supported one - as agreed in https://lists.apache.org/thread/0oxnvct24xlqsj76z42w2ttw2d043oy3

However as observed and tracked in #36740 the change was not effective. We only changed the moment at which latest image is pointing to 2.8.0 but not whether 2.8.0 points to python-3.8 or `python-3.11'.

This means that we should only do that change for Python 3.9 qnd revert the changelog (and cherry-pick it to 2.8.1)


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

In apache#36003 we **thought** we changed default "version" image to
point to "newest" python version not to the "oldest" supported
one - as agreed in https://lists.apache.org/thread/0oxnvct24xlqsj76z42w2ttw2d043oy3

However as observed and tracked in apache#36740 the change was not effective.
We only changed the moment at which latest image is pointing to
2.8.0 but not whether 2.8.0 points to `python-3.8` or `python-3.11'.

This means that we should only do that change for Python 3.9 qnd
revert the changelog (and cherry-pick it to 2.8.1)
@boring-cyborg boring-cyborg bot added area:production-image Production image improvements and fixes kind:documentation labels Jan 14, 2024
@potiuk potiuk requested a review from ephraimbuddy January 14, 2024 21:24
@potiuk potiuk added this to the Airflow 2.8.1 milestone Jan 14, 2024
@potiuk
Copy link
Member Author

potiuk commented Jan 14, 2024

We should merge that one to 2.8.1 - this is a changelog fix only

potiuk added a commit to potiuk/airflow that referenced this pull request Jan 14, 2024
The change apache#36003 attempted to change which Python version is used
for the "default" image ("2.8.0" and effectively "latest as well).

But it failed to do so - because of a bug. The changelog about this
have been removed in apache#36777 and we are bringing the change back
(this time properly implemented) and changelog - with aim to
release it in Airflow 2.9.0.

Fixes: apache#36740
@potiuk potiuk merged commit 270b112 into apache:main Jan 14, 2024
@potiuk potiuk deleted the remove-changelog-about-not-implemented-change branch January 14, 2024 21:45
@potiuk
Copy link
Member Author

potiuk commented Jan 14, 2024

Cherry-picked to 2.8.1 @ephraimbuddy

potiuk added a commit that referenced this pull request Jan 15, 2024
The change #36003 attempted to change which Python version is used
for the "default" image ("2.8.0" and effectively "latest as well).

But it failed to do so - because of a bug. The changelog about this
have been removed in #36777 and we are bringing the change back
(this time properly implemented) and changelog - with aim to
release it in Airflow 2.9.0.

Fixes: #36740
ephraimbuddy pushed a commit that referenced this pull request Jan 15, 2024
)

In #36003 we **thought** we changed default "version" image to
point to "newest" python version not to the "oldest" supported
one - as agreed in https://lists.apache.org/thread/0oxnvct24xlqsj76z42w2ttw2d043oy3

However as observed and tracked in #36740 the change was not effective.
We only changed the moment at which latest image is pointing to
2.8.0 but not whether 2.8.0 points to `python-3.8` or `python-3.11'.

This means that we should only do that change for Python 3.9 qnd
revert the changelog (and cherry-pick it to 2.8.1)

(cherry picked from commit 270b112)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:production-image Production image improvements and fixes kind:documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants