Table of contents

Selecting what to put into the release
- Selecting what to cherry-pick
- Reviewing cherry-picked PRs and assigning labels
Prepare the Apache Airflow Package RC
Verify the release candidate by PMCs
Verify release candidates by Contributors
Publish the final Apache Airflow release

You can find the prerequisites to release Apache Airflow in README.md.

Selecting what to put into the release

The first step of a release is to work out what is being included. This differs based on whether it is a major/minor or a patch release.

For a major or minor release, you want to include everything in main at the time of release; you'll turn this into a new release branch as part of the rest of the process.
For a patch release, you will be selecting specific commits to cherry-pick and backport into the existing release branch.

Selecting what to cherry-pick

For obvious reasons, you can‘t cherry-pick every change from main into the release branch - some are incompatible without a large set of other changes, some are brand-new features, and some just don’t need to be in a release.

In general only security fixes, data-loss bugs and regression fixes are essential to bring into a patch release; also changes in dependencies (setup.py, setup.cfg) resulting from releasing newer versions of packages that Airflow depends on. Other bugfixes can be added on a best-effort basis, but if something is going to be very difficult to backport (maybe it has a lot of conflicts, or heavily depends on a new feature or API that‘s not being backported), it’s OK to leave it out of the release at your sole discretion as the release manager - if you do this, update the milestone in the issue to the “next” minor release.

Many issues will be marked with the target release as their Milestone; this is a good shortlist to start with for what to cherry-pick.

For a patch release, find out other bug fixes that are not marked with the target release as their Milestone and mark those as well. You can accomplish this by running the following command:

 ./dev/airflow-github needs-categorization 2.3.2 HEAD

Often you also want to cherry-pick changes related to CI and development tools, to include the latest stability fixes in CI and improvements in development tools. Usually you can see the list of such changes via (this will exclude already merged changes:

git fetch apache
git log --oneline apache/v2-2-test | sed -n 's/.*\((#[0-9]*)\)$/\1/p' > /tmp/merged
git log --oneline --decorate apache/v2-2-stable..apache/main -- Dockerfile* scripts breeze* .github/ setup* dev | grep -vf /tmp/merged

Most of those PRs should be marked with changelog:skip label, so that they are excluded from the user-facing changelog as they only matter for developers of Airflow. We have a tool that allows to easily review the cherry-picked PRs and mark them with the right label - see below.

You also likely want to cherry-pick some of the latest doc changes in order to bring clarification and explanations added to the documentation. Usually you can see the list of such changes via:

git fetch apache
git log --oneline apache/v2-2-test | sed -n 's/.*\((#[0-9]*)\)$/\1/p' > /tmp/merged
git log --oneline --decorate apache/v2-2-stable..apache/main -- docs/apache-airflow docs/docker-stack/ | grep -vf /tmp/merged

Those changes that are “doc-only” changes should be marked with type:doc-only label so that they land in documentation part of the changelog. The tool to review and assign the labels is described below.

When you cherry-pick, pick in chronological order onto the vX-Y-test release branch. You'll move them over to be on vX-Y-stable once the release is cut.

Reviewing cherry-picked PRs and assigning labels

We have the tool that allows to review cherry-picked PRs and assign the labels ./assign_cherry_picked_prs_with_milestone.py

It allows to manually review and assign milestones and labels to cherry-picked PRs:

./dev/assign_cherry_picked_prs_with_milestone.py assign-prs --previous-release v2-2-stable --current-release apache/v2-2-test --milestone-number 48

It summarises the state of each cherry-picked PR including information whether it is going to be excluded or included in changelog or included in doc-only part of it. It also allows to re-assign the PRs to the target milestone and apply the changelog:skip or type:doc-only label.

You can also add --skip-assigned flag if you want to automatically skip the question of assignment for the PRs that are already correctly assigned to the milestone. You can also avoid the “Are you OK?” question with --assume-yes flag.

You cn review the list of PRs cherry-picked and produce a nice summary with --print-summary (this flag assumes the --skip-assigned flag, so that the summary can be produced without questions:

./dev/assign_cherry_picked_prs_with_milestone.py assign-prs --previous-release v2-2-stable \
  --current-release apache/v2-2-test --milestone-number 48 --skip-assigned --assume-yes --print-summary \
  --output-folder /tmp

This will produce summary output with nice links that you can use to review the cherry-picked changes, but it also produces files with list of commits separated by type in the folder specified. In the case above, it will produce three files that you can use in the next step:

Changelog commits written in /tmp/changelog-changes.txt

Doc only commits written in /tmp/doc-only-changes.txt

Excluded commits written in /tmp/excluded-changes.txt

You can see for example which files have been changed by “doc-only” or “excluded” changes, to make sure that no “sneaky” changes were by mistake classified wrongly.

git show --format=tformat:"" --stat --name-only $(cat /tmp/doc-only-changes.txt) | sort | uniq

Then if you see suspicious file (example airflow/sensors/base.py) you can find details on where they came from:

git log apache/v2-2-test --format="%H" -- airflow/sensors/base.py | grep -f /tmp/doc-only-changes.txt | xargs git show

And the URL to the PR it comes from:

git log apache/v2-2-test --format="%H" -- airflow/sensors/base.py | grep -f /tmp/doc-only-changes.txt | \
    xargs -n 1 git log --oneline --max-count=1 | \
    sed s'/.*(#\([0-9]*\))$/https:\/\/github.com\/apache\/airflow\/pull\/\1/'

Prepare the Apache Airflow Package RC

Update the milestone

Before cutting an RC, we should look at the milestone and merge anything ready, or if we aren't going to include it in the release we should update the milestone for those issues. We should do that before cutting the RC so the milestone gives us an accurate view of what is going to be in the release as soon as we know what it will be.

Build RC artifacts

The Release Candidate artifacts we vote upon should be the exact ones we vote against, without any modification other than renaming – i.e. the contents of the files must be the same between voted release candidate and final release. Because of this the version in the built artifacts that will become the official Apache releases must not include the rcN suffix.

Set environment variables

# Set Version
export VERSION=2.1.2rc3
export VERSION_SUFFIX=rc3
export VERSION_BRANCH=2-1
export VERSION_WITHOUT_RC=${VERSION/rc?/}

# Set AIRFLOW_REPO_ROOT to the path of your git repo
export AIRFLOW_REPO_ROOT=$(pwd)


# Example after cloning
git clone https://github.com/apache/airflow.git airflow
cd airflow
export AIRFLOW_REPO_ROOT=$(pwd)

Check out the ‘test’ branch
For major/minor version release, please follow the instructions at Prepare new release branches and cache to create the ‘test’ and ‘stable’ branches.
```
git checkout v${VERSION_BRANCH}-test
```
Set your version in setup.py (without the RC tag)
Add supported Airflow version to ./scripts/ci/pre_commit/pre_commit_supported_versions.py and let pre-commit do the job
Replace the version in README.md and verify that installation instructions work fine.
Build the release notes:
Preview with:
```
towncrier build --draft --version=${VERSION_WITHOUT_RC} --date=2021-12-15 --dir . --config newsfragments/config.toml
```
Then remove the --draft flag to have towncrier build the release notes for real.
If no significant changes where added in this release, add the header and put “No significant changes.” (e.g. 2.1.4).
Update the REVISION_HEADS_MAP at airflow/utils/db.py to include the revision head of the release even if there are no migrations.
Commit the version change.
Check out the ‘stable’ branch
```
git checkout v${VERSION_BRANCH}-stable
```
PR from the ‘test’ branch to the ‘stable’ branch, and manually merge it once approved. Here's how to manually merge the PR:
```
git merge --ff-only v${VERSION_BRANCH}-test
```

Tag your release

git tag -s ${VERSION} -m "Apache Airflow ${VERSION}"

Clean the checkout repo
```
git clean -fxd
```
Restore breeze installation (The breeze's .egginfo is cleared by git-clean)
```
pipx install -e ./dev/breeze --force
```
Make sure you have the latest CI image
```
breeze ci-image build --python 3.7
```

Tarball the repo

mkdir dist
git archive --format=tar.gz ${VERSION} \
    --prefix=apache-airflow-${VERSION_WITHOUT_RC}/ \
    -o dist/apache-airflow-${VERSION_WITHOUT_RC}-source.tar.gz

Copy the tarball to a location outside of the repo and verify licences.

Generate SHA512/ASC (If you have not generated a key yet, generate it by following instructions on http://www.apache.org/dev/openpgp.html#key-gen-generate-key)
```
breeze release-management prepare-airflow-package --package-format both
pushd dist
${AIRFLOW_REPO_ROOT}/dev/sign.sh *
popd
```

If you aren't using Breeze for packaging, build the distribution and wheel files directly

python setup.py compile_assets sdist bdist_wheel
pushd dist
${AIRFLOW_REPO_ROOT}/dev/sign.sh *
popd

Tag & Push the constraints files. This pushes constraints with rc suffix (this is expected)!

git checkout origin/constraints-${VERSION_BRANCH}
git tag -s "constraints-${VERSION}" -m "Constraints for Apache Airflow ${VERSION}"
git push origin "constraints-${VERSION}"

Push the artifacts to ASF dev dist repo

# First clone the repo

[ -d asf-dist ] || svn checkout --depth=immediates https://dist.apache.org/repos/dist asf-dist
svn update --set-depth=infinity asf-dist/dev/airflow
cd asf-dist/dev/airflow

# Create new folder for the release
svn mkdir ${VERSION}

# Move the artifacts to svn folder & commit
mv ${AIRFLOW_REPO_ROOT}/dist/* ${VERSION}/
cd ${VERSION}
svn add *
svn commit -m "Add artifacts for Airflow ${VERSION}"

Prepare new release branches and cache - optional when first minor version is released

When you just released the X.Y.0 version (first release of new minor version) you need to create release branches: vX-Y-test and vX-Y-stable (for example with 2.1.0rc1 release you need to create v2-1-test and v2-1-stable branches). You also need to configure the branch

Create test source branch

# First clone the repo
export BRANCH_PREFIX=2-1
git branch v${BRANCH_PREFIX}-test

Re-tag images from main

Run script to re-tag images from the main branch to the vX-Y-test branch:

./dev/retag_docker_images.py --source-branch main --target-branch v${BRANCH_PREFIX}-test

Update default branches

In the legacy, bash breeze (to be removed when the bash breeze is entirely gone)

In ./scripts/ci/libraries/_intialization.sh update branches to reflect the new branch:

export DEFAULT_BRANCH=${DEFAULT_BRANCH="main"}
export DEFAULT_CONSTRAINTS_BRANCH=${DEFAULT_CONSTRAINTS_BRANCH="constraints-main"}

should become this, where X-Y is your new branch version:

export DEFAULT_BRANCH=${DEFAULT_BRANCH="vX-Y-test"}
export DEFAULT_CONSTRAINTS_BRANCH=${DEFAULT_CONSTRAINTS_BRANCH="constraints-X-Y"}

In ./scripts/ci/libraries/_build_images.sh add branch to preload packages from (replace X and Y in values for comparison and regexp):

    elif [[ ${AIRFLOW_VERSION} =~ v?X\.Y* ]]; then
        AIRFLOW_BRANCH_FOR_PYPI_PRELOADING="vX-Y-stable"

In the new breeze

In ./dev/breeze/src/airflow_breeze/branch_defaults.py update branches to reflect the new branch:

AIRFLOW_BRANCH = "main"
DEFAULT_AIRFLOW_CONSTRAINTS_BRANCH = "constraints-main"

should become this, where X-Y is your new branch version:

AIRFLOW_BRANCH = "vX-Y-test"
DEFAULT_AIRFLOW_CONSTRAINTS_BRANCH = "constraints-X-Y"

Commit the changes to the test branch

git add -p .
git commit "Update default branches for ${BRANCH_PREFIX}"

Create stable branch

git branch v${BRANCH_PREFIX}-stable

Push test and stable branch

git checkout v${BRANCH_PREFIX}-test
git push --set-upstream origin v${BRANCH_PREFIX}-test
git checkout v${BRANCH_PREFIX}-stable
git push --set-upstream origin v${BRANCH_PREFIX}-stable

Add branches in the main branch

You have to do those steps in the main branch of the repository:

git checkout main
git pull

Add vX-Y-stable and vX-Y-test branches in codecov.yml (there are 2 places in the file!)

    branches:
      - main
      - v2-0-stable
      - v2-0-test
      - v2-1-stable
      - v2-1-test
      - v2-2-stable
      - v2-2-test

Add vX-Y-stable to .asf.yaml (X-Y is your new branch)

protected_branches:
    main:
        required_pull_request_reviews:
        required_approving_review_count: 1
    ...
    vX-Y-stable:
        required_pull_request_reviews:
        required_approving_review_count: 1

Create constraints branch out of the constraints-main one

# First clone the repo
export BRANCH_PREFIX=2-1
git checkout constraints-main
git checkout -b constraints-${BRANCH_PREFIX}
git push --set-upstream origin constraints-${BRANCH_PREFIX}

Prepare PyPI convenience “snapshot” packages

At this point we have the artifact that we vote on, but as a convenience to developers we also want to publish “snapshots” of the RC builds to PyPI for installing via pip:

To do this we need to

Checkout the rc tag:

cd "${AIRFLOW_REPO_ROOT}"
git checkout ${VERSION}

Build the package:

breeze release-management prepare-airflow-package --version-suffix-for-pypi "${VERSION_SUFFIX}" --package-format both

Verify the artifacts that would be uploaded:
```
twine check dist/*
```
Upload the package to PyPI's test environment:
```
twine upload -r pypitest dist/*
```
Verify that the test package looks good by downloading it and installing it into a virtual environment. The package download link is available at: https://test.pypi.org/project/apache-airflow/#files
Upload the package to PyPI's production environment:
```
twine upload -r pypi dist/*
```
Again, confirm that the package is available here: https://pypi.python.org/pypi/apache-airflow

It is important to stress that this snapshot should not be named “release”, and it is not supposed to be used by and advertised to the end-users who do not read the devlist.

Push Tag for the release candidate
This step should only be done now and not before, because it triggers an automated build of the production docker image, using the packages that are currently released in PyPI (both airflow and latest provider packages).
```
git push origin tag ${VERSION}
```

Prepare production Docker Image RC

Production Docker images should be manually prepared and pushed by the release manager or another committer who has access to Airflow's DockerHub. Note that we started releasing a multi-platform build, so you need to have an environment prepared to build multi-platform images. You can achieve it with:

GitHub Actions Manual Job (easiest)
Emulation (very slow)
Hardware builders if you have both AMD64 and ARM64 hardware locally

Building the image is triggered by running the Release PROD Images workflow.

When you trigger it you need to pass:

Airflow Version (including the right rc suffix)
Optional “true” in the “Skip latest:” field if you do not want to re-tag the latest image

Release prod image

The manual building is described in MANUALLY_BUILDING_IMAGES.md.

Prepare issue for testing status of rc

For now this part works for bugfix releases only, for major/minor ones we will experiment and see if there is a way to only extract important/not tested bugfixes and high-level changes to make the process manageable.

Create an issue for testing status of the RC (PREVIOUS_RELEASE should be the previous release version (for example 2.1.0).

cat <<EOF
Status of testing of Apache Airflow ${VERSION}
EOF

Content is generated with:

./dev/prepare_release_issue.py generate-issue-content --previous-release <PREVIOUS_RELEASE> \
    --current-release ${VERSION}

Copy the URL of the issue.

Prepare Vote email on the Apache Airflow release candidate

Send out a vote to the dev@airflow.apache.org mailing list:

Subject:

cat <<EOF
[VOTE] Release Airflow ${VERSION_WITHOUT_RC} from ${VERSION}
EOF

Body:

cat <<EOF
Hey fellow Airflowers,

I have cut Airflow ${VERSION}. This email is calling a vote on the release,
which will last at least 72 hours, from Friday, October 8, 2021 at 4:00 pm UTC
until Monday, October 11, 2021 at 4:00 pm UTC, and until 3 binding +1 votes have been received.

https://www.timeanddate.com/worldclock/fixedtime.html?msg=8&iso=20211011T1600&p1=1440

Status of testing of the release is kept in TODO:URL_OF_THE_ISSUE_HERE

Consider this my (binding) +1.

Airflow ${VERSION} is available at:
https://dist.apache.org/repos/dist/dev/airflow/$VERSION/

*apache-airflow-${VERSION_WITHOUT_RC}-source.tar.gz* is a source release that comes with INSTALL instructions.
*apache-airflow-${VERSION_WITHOUT_RC}.tar.gz* is the binary Python "sdist" release.
*apache_airflow-${VERSION_WITHOUT_RC}-py3-none-any.whl* is the binary Python wheel "binary" release.

Public keys are available at:
https://dist.apache.org/repos/dist/release/airflow/KEYS

Please vote accordingly:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Only votes from PMC members are binding, but all members of the community
are encouraged to test the release and vote with "(non-binding)".

The test procedure for PMCs and Contributors who would like to test this RC are described in
https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOW.md#verify-the-release-candidate-by-pmcs

Please note that the version number excludes the \`rcX\` string, so it's now
simply ${VERSION_WITHOUT_RC}. This will allow us to rename the artifact without modifying
the artifact checksums when we actually release.

Release Notes: https://github.com/apache/airflow/blob/${VERSION}/RELEASE_NOTES.rst

Changes since PREVIOUS_VERSION_OR_RC:
*Bugs*:
[AIRFLOW-3732] Fix issue when trying to edit connection in RBAC UI
[AIRFLOW-2866] Fix missing CSRF token head when using RBAC UI (#3804)
...


*Improvements*:
[AIRFLOW-3302] Small CSS fixes (#4140)
[Airflow-2766] Respect shared datetime across tabs
...


*New features*:
[AIRFLOW-2874] Enables FAB's theme support (#3719)
[AIRFLOW-3336] Add new TriggerRule for 0 upstream failures (#4182)
...


*Doc-only Change*:
[AIRFLOW-XXX] Fix BashOperator Docstring (#4052)
[AIRFLOW-3018] Fix Minor issues in Documentation
...

Cheers,
<your name>
EOF

Verify the release candidate by PMCs

The PMCs should verify the releases in order to make sure the release is following the Apache Legal Release Policy.

At least 3 (+1) votes should be recorded in accordance to Votes on Package Releases

The legal checks include:

checking if the packages are present in the right dist folder on svn
verifying if all the sources have correct licences
verifying if release manager signed the releases with the right key
verifying if all the checksums are valid for the release

SVN check

The files should be present in the sub-folder of Airflow dist

The following files should be present (9 files):

-source.tar.gz + .asc + .sha512
.tar.gz + .asc + .sha512
-py3-none-any.whl + .asc + .sha512

As a PMC you should be able to clone the SVN repository:

svn co https://dist.apache.org/repos/dist/dev/airflow

Or update it if you already checked it out:

svn update .

Optionally you can use check_files.py script to verify that all expected files are present in SVN. This script may help also with verifying installation of the packages.

python check_files.py airflow -v {VERSION} -p {PATH_TO_SVN}

Licence check

This can be done with the Apache RAT tool.

Download the latest jar from https://creadur.apache.org/rat/download_rat.cgi (unpack the binary, the jar is inside)
Unpack the release source archive (the <package + version>-source.tar.gz file) to a folder
Enter the sources folder run the check

java -jar ../../apache-rat-0.13/apache-rat-0.13.jar -E .rat-excludes -d .

where .rat-excludes is the file in the root of Airflow source code.

Signature check

Make sure you have imported into your GPG the PGP key of the person signing the release. You can find the valid keys in KEYS.

You can import the whole KEYS file:

gpg --import KEYS

You can also import the keys individually from a keyserver. The below one uses Kaxil's key and retrieves it from the default GPG keyserver OpenPGP.org:

gpg --keyserver keys.openpgp.org --receive-keys CDE15C6E4D3A8EC4ECF4BA4B6674E08AD7DE406F

You should choose to import the key when asked.

Note that by being default, the OpenPGP server tends to be overloaded often and might respond with errors or timeouts. Many of the release managers also uploaded their keys to the GNUPG.net keyserver, and you can retrieve it from there.

gpg --keyserver keys.gnupg.net --receive-keys CDE15C6E4D3A8EC4ECF4BA4B6674E08AD7DE406F

Once you have the keys, the signatures can be verified by running this:

for i in *.asc
do
   echo -e "Checking $i\n"; gpg --verify $i
done

This should produce results similar to the below. The “Good signature from ...” is indication that the signatures are correct. Do not worry about the “not certified with a trusted signature” warning. Most of the certificates used by release managers are self-signed, and that‘s why you get this warning. By importing the key either from the server in the previous step or from the KEYS page, you know that this is a valid key already. To suppress the warning you may edit the key’s trust level by running gpg --edit-key <key id> trust and entering 5 to assign trust level ultimate.

Checking apache-airflow-2.0.2rc4.tar.gz.asc
gpg: assuming signed data in 'apache-airflow-2.0.2rc4.tar.gz'
gpg: Signature made sob, 22 sie 2020, 20:28:28 CEST
gpg:                using RSA key 12717556040EEF2EEAF1B9C275FCCD0A25FA0E4B
gpg: Good signature from "Kaxil Naik <kaxilnaik@gmail.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 1271 7556 040E EF2E EAF1  B9C2 75FC CD0A 25FA 0E4B

Checking apache_airflow-2.0.2rc4-py2.py3-none-any.whl.asc
gpg: assuming signed data in 'apache_airflow-2.0.2rc4-py2.py3-none-any.whl'
gpg: Signature made sob, 22 sie 2020, 20:28:31 CEST
gpg:                using RSA key 12717556040EEF2EEAF1B9C275FCCD0A25FA0E4B
gpg: Good signature from "Kaxil Naik <kaxilnaik@gmail.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 1271 7556 040E EF2E EAF1  B9C2 75FC CD0A 25FA 0E4B

Checking apache-airflow-2.0.2rc4-source.tar.gz.asc
gpg: assuming signed data in 'apache-airflow-2.0.2rc4-source.tar.gz'
gpg: Signature made sob, 22 sie 2020, 20:28:25 CEST
gpg:                using RSA key 12717556040EEF2EEAF1B9C275FCCD0A25FA0E4B
gpg: Good signature from "Kaxil Naik <kaxilnaik@gmail.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 1271 7556 040E EF2E EAF1  B9C2 75FC CD0A 25FA 0E4B

SHA512 sum check

Run this:

for i in *.sha512
do
    echo "Checking $i"; shasum -a 512 `basename $i .sha512 ` | diff - $i
done

You should get output similar to:

Checking apache-airflow-2.0.2rc4.tar.gz.sha512
Checking apache_airflow-2.0.2rc4-py2.py3-none-any.whl.sha512
Checking apache-airflow-2.0.2rc4-source.tar.gz.sha512

Verify release candidates by Contributors

This can be done (and we encourage to) by any of the Contributors. In fact, it's best if the actual users of Apache Airflow test it in their own staging/test installations. Each release candidate is available on PyPI apart from SVN packages, so everyone should be able to install the release candidate version of Airflow via simply ( is 2.0.2 for example, and is release candidate number 1,2,3,....).

pip install apache-airflow==<VERSION>rc<X>

Optionally it can be followed with constraints

pip install apache-airflow==<VERSION>rc<X> \
  --constraint "https://raw.githubusercontent.com/apache/airflow/constraints-<VERSION>/constraints-3.7.txt"`

Note that the constraints contain python version that you are installing it with.

You can use any of the installation methods you prefer (you can even install it via the binary wheel downloaded from the SVN).

There is also an easy way of installation with Breeze if you have the latest sources of Apache Airflow. Running the following command will use tmux inside breeze, create admin user and run Webserver & Scheduler:

breeze start-airflow --use-airflow-version <VERSION>rc<X> --python 3.7 --backend postgres

Once you install and run Airflow, you should perform any verification you see as necessary to check that the Airflow works as you expected.

Publish the final Apache Airflow release

Summarize the voting for the Apache Airflow release

Once the vote has been passed, you will need to send a result vote to dev@airflow.apache.org:

Subject:

[RESULT][VOTE] Release Airflow 2.0.2 from 2.0.2rc3

Message:

Hello,

Apache Airflow 2.0.2 (based on RC3) has been accepted.

4 "+1" binding votes received:
- Kaxil Naik
- Bolke de Bruin
- Ash Berlin-Taylor
- Tao Feng


4 "+1" non-binding votes received:

- Deng Xiaodong
- Stefan Seelmann
- Joshua Patchus
- Felix Uellendall

Vote thread:
https://lists.apache.org/thread.html/736404ca3d2b2143b296d0910630b9bd0f8b56a0c54e3a05f4c8b5fe@%3Cdev.airflow.apache.org%3E

I'll continue with the release process, and the release announcement will follow shortly.

Cheers,
<your name>

Publish release to SVN

You need to migrate the RC artifacts that passed to this repository: https://dist.apache.org/repos/dist/release/airflow/ (The migration should include renaming the files so that they no longer have the RC number in their filenames.)

The best way of doing this is to svn cp between the two repos (this avoids having to upload the binaries again, and gives a clearer history in the svn commit logs):

# GO to Airflow Sources first
cd <YOUR_AIRFLOW_REPO_ROOT>
export AIRFLOW_REPO_ROOT="$(pwd)"
cd ..

[ -d asf-dist ] || svn checkout --depth=immediates https://dist.apache.org/repos/dist asf-dist
svn update --set-depth=infinity asf-dist/{release,dev}/airflow
AIRFLOW_DEV_SVN="${PWD}/asf-dist/dev/airflow"
cd asf-dist/release/airflow

export RC=2.0.2rc5
export VERSION=${RC/rc?/}

# Create new folder for the release
svn mkdir "${VERSION}"
cd "${VERSION}"

# Move the artifacts to svn folder & commit
for f in ${AIRFLOW_DEV_SVN}/$RC/*; do
    svn cp "$f" "${$(basename $f)/}"
done
svn commit -m "Release Airflow ${VERSION} from ${RC}"

# Remove old release
# See http://www.apache.org/legal/release-policy.html#when-to-archive
cd ..
export PREVIOUS_VERSION=2.0.2
svn rm "${PREVIOUS_VERSION}"
svn commit -m "Remove old release: ${PREVIOUS_VERSION}"

Verify that the packages appear in airflow

Prepare PyPI “release” packages

At this point we release an official package:

Verify the artifacts that would be uploaded:

cd "${AIRFLOW_RELEASE_SVN}/${VERSION}"
twine check *.whl *${VERSION}.tar.gz

Upload the package to PyPI's test environment:

twine upload -r pypitest *.whl *${VERSION}.tar.gz

Verify that the test package looks good by downloading it and installing it into a virtual environment. The package download link is available at: https://test.pypi.org/project/apache-airflow/#files
Upload the package to PyPI's production environment:
```
twine upload -r pypi *.whl *${VERSION}.tar.gz
```
Again, confirm that the package is available here: https://pypi.python.org/pypi/apache-airflow

Re-Tag & Push the constraints files with the final release version.

cd "${AIRFLOW_REPO_ROOT}"
git checkout constraints-${RC}
git tag -s "constraints-${VERSION}" -m "Constraints for Apache Airflow ${VERSION}"
git push origin tag "constraints-${VERSION}"

In case you release “latest stable” version, also update “latest” constraints

git tag -f -s "constraints-latest" -m "Latest constraints set to Apache Airflow ${VERSION}"
git push -f origin tag "constraints-latest"

Push Tag for the final version
This step should only be done now and not before, because it triggers an automated build of the production docker image, using the packages that are currently released in PyPI (both airflow and latest provider packages).
```
git checkout ${RC}
git tag -s ${VERSION} -m "Apache Airflow ${VERSION}"
git push origin tag ${VERSION}
```

Manually prepare production Docker Image

Building the image is triggered by running the Release PROD Images workflow.

When you trigger it you need to pass:

Airflow Version
Optional “true” in skip latest field if you do not want to retag the latest image

Release prod image

Note that by default the latest images tagged are aliased to the just released image which is the usual way we release. For example when you are releasing 2.3.N image and 2.3 is our latest branch the new image is marked as “latest”.

In case we are releasing (which almost never happens so far) a critical bugfix release in one of the older branches, you should set the “skip” field to true.

Verify production images

for PYTHON in 3.7 3.8 3.9 3.10
do
    docker pull apache/airflow:${VERSION}-python${PYTHON}
    breeze prod-image verify --image-name apache/airflow:${VERSION}-python${PYTHON}
done
docker pull apache/airflow:${VERSION}
breeze prod-image verify --image-name apache/airflow:${VERSION}

Publish documentation

Documentation is an essential part of the product and should be made available to users. In our cases, documentation for the released versions is published in a separate repository - apache/airflow-site, but the documentation source code and build tools are available in the apache/airflow repository, so you have to coordinate between the two repositories to be able to build the documentation.

Documentation for providers can be found in the /docs/apache-airflow directory.

First, copy the airflow-site repository and set the environment variable AIRFLOW_SITE_DIRECTORY.

git clone https://github.com/apache/airflow-site.git airflow-site
cd airflow-site
git checkout -b ${VERSION}-docs
export AIRFLOW_SITE_DIRECTORY="$(pwd)"

Then you can go to the directory and build the necessary documentation packages

cd "${AIRFLOW_REPO_ROOT}"
breeze build-docs --package-filter apache-airflow --package-filter docker-stack --clean-build --for-production

Now you can preview the documentation.
```
./docs/start_doc_server.sh
```

Copy the documentation to the airflow-site repository, create commit, push changes and open a PR.

./docs/publish_docs.py --package-filter apache-airflow --package-filter docker-stack
cd "${AIRFLOW_SITE_DIRECTORY}"
git add .
git commit -m "Add documentation for Apache Airflow ${VERSION}"
git push
# and finally open a PR

Notify developers of release

Notify users@airflow.apache.org (cc'ing dev@airflow.apache.org) that the artifacts have been published:

Subject:

cat <<EOF
[ANNOUNCE] Apache Airflow ${VERSION} Released
EOF

Body:

cat <<EOF
Dear Airflow community,

I'm happy to announce that Airflow ${VERSION} was just released.

The released sources and packages can be downloaded via https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-sources.html

Other installation methods are described in https://airflow.apache.org/docs/apache-airflow/stable/installation/

We also made this version available on PyPI for convenience:
\`pip install apache-airflow\`
https://pypi.org/project/apache-airflow/${VERSION}/

The documentation is available at:
https://airflow.apache.org/docs/apache-airflow/${VERSION}/

Find the release notes here for more details:
https://airflow.apache.org/docs/apache-airflow/${VERSION}/release_notes.html

Container images are published at:
https://hub.docker.com/r/apache/airflow/tags/?page=1&name=${VERSION}

Cheers,
<your name>
EOF

Send the same email to announce@apache.org, except change the opening line to Dear community,. It is more reliable to send it via the web ui at https://lists.apache.org/list.html?announce@apache.org (press “c” to compose a new thread)

Add release data to Apache Committee Report Helper

Add the release data (version and date) at: https://reporter.apache.org/addrelease.html?airflow

Update Announcements page

Update “Announcements” page at the Official Airflow website

Create release on GitHub

Create a new release on GitHub with the release notes and assets from the release svn.

Close the milestone

Close the milestone on GitHub. Create the next one if it hasn't been already (it probably has been). Update the new milestone in the Currently we are working on issue make sure to update the last updated timestamp as well.

Close the testing status issue

Don't forget to thank the folks who tested and close the issue tracking the testing status.

Announce the release on the community slack

Post this in the #announce channel:

cat <<EOF
We've just released Apache Airflow $VERSION 🎉

📦 PyPI: https://pypi.org/project/apache-airflow/$VERSION/
📚 Docs: https://airflow.apache.org/docs/apache-airflow/$VERSION/
🛠 Release Notes: https://airflow.apache.org/docs/apache-airflow/$VERSION/release_notes.html
🐳 Docker Image: "docker pull apache/airflow:$VERSION"
🚏 Constraints: https://github.com/apache/airflow/tree/constraints-$VERSION

Thanks to all the contributors who made this possible.
EOF

Tweet about the release

Tweet about the release:

cat <<EOF
We've just released Apache Airflow $VERSION 🎉

📦 PyPI: https://pypi.org/project/apache-airflow/$VERSION/
📚 Docs: https://airflow.apache.org/docs/apache-airflow/$VERSION/
🛠 Release Notes: https://airflow.apache.org/docs/apache-airflow/$VERSION/release_notes.html
🐳 Docker Image: "docker pull apache/airflow:$VERSION"

Thanks to all the contributors who made this possible.
EOF

Update `main` with the latest release details

This includes:

Modify ./scripts/ci/pre_commit/pre_commit_supported_versions.py and let pre-commit do the job
For major/minor release, Update version in setup.py and docs/docker-stack/ to the next likely minor version release.
Update the REVISION_HEADS_MAP at airflow/utils/db.py to include the revision head of the release even if there are no migrations.
Sync RELEASE_NOTES.rst (including deleting relevant newsfragments) and README.md changes
Updating airflow_bug_report.yml issue template in .github/ISSUE_TEMPLATE/ with the new version
Updating Dockerfile with the new version

Update default Airflow version in the helm chart

Update the values of airflowVersion, defaultAirflowTag and appVersion in the helm chart so the next helm chart release will use the latest released version. You'll need to update chart/values.yaml, chart/values.schema.json and chart/Chart.yaml.

Also add a note to UPDATING.rst that the default version of Airflow has changed.

In chart/Chart.yaml, make sure the screenshot annotations are still all valid URLs.

Update airflow/config_templates/config.yml file

File airflow/config_templates/config.yml contains documentation on all configuration options available in Airflow. The version_added fields must be updated when a new Airflow version is released.

Get a diff between the released versions and the current local file on main branch:
```
./dev/validate_version_added_fields_in_config.py
```
Update airflow/config_templates/config.yml with the details, and commit it.

Update EndOfLife data

Make a PR EndOfLife with release date, latest version and updated changelog link.

Selecting what to put into the release

Selecting what to cherry-pick

Reviewing cherry-picked PRs and assigning labels

Prepare the Apache Airflow Package RC

Update the milestone

Build RC artifacts

Prepare new release branches and cache - optional when first minor version is released

Create test source branch

Re-tag images from main

Update default branches

In the legacy, bash breeze (to be removed when the bash breeze is entirely gone)

In the new breeze

Commit the changes to the test branch

Create stable branch

Push test and stable branch

Add branches in the main branch

Create constraints branch out of the constraints-main one

Prepare PyPI convenience “snapshot” packages

Prepare production Docker Image RC

Prepare issue for testing status of rc

Prepare Vote email on the Apache Airflow release candidate

Verify the release candidate by PMCs

SVN check

Licence check

Signature check

SHA512 sum check

Verify release candidates by Contributors

Publish the final Apache Airflow release

Summarize the voting for the Apache Airflow release

Publish release to SVN

Prepare PyPI “release” packages

Manually prepare production Docker Image

Verify production images

Publish documentation

Notify developers of release

Add release data to Apache Committee Report Helper

Update Announcements page

Create release on GitHub

Close the milestone

Close the testing status issue

Announce the release on the community slack

Tweet about the release

Update main with the latest release details

Update default Airflow version in the helm chart

Update airflow/config_templates/config.yml file

Update EndOfLife data

Update `main` with the latest release details