DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
Building an RC
The Release Candidate artefacts we vote upon should be the exact ones we vote against, without any modification than renaming – i.e. the contents of the files must be the same between voted release canidate and final release. Because of this the version in the built artefacts that will become the official Apache releases must not include the rcN suffix.
export VERSION=1.10.0rc1- set your version to 1.10.0 in
airflow/version.py(without the RC tag) - Commit the version change.
tag your release
git tag ${VERSION}Clean the checkout: the sdist step below will
git clean -fxd# tarball the repogit archive --format=tar.gz ${VERSION} --prefix=apache-airflow-${VERSION}+incubating/ -o apache-airflow-${VERSION}+incubating-source.tar.gz- generate sdist
NOTE: Make sure your checkout is clean at this stage - any untracked or changed files will otherwise be included in the file produced.python setup.py sdist - Rename the sdist to apache-airflow-${VERSION}+incubating-bin.tar.gz
Generate MD5/SHA512/ASC
</path to airflow source>/dev/sign.sh apache-airflow-${VERSION}+incubating-source.tar.gz && </path to airflow source>/dev/sign.sh apache-airflow-${VERSION}+incubating-bin.tar.gzgit push --tags
At this point we have the artefact that we vote on, but as a convenience to our users we also want to publish "snapshots" of the RC builds to pypi for installing via pip. To do this we need to
- Edit the
airflow/version.pyto include the RC suffix. python setup.py sdist- Follow the steps in Releasing Airflow
Voting on an RC
Once the RC is built (both source and binary), put them in the dev SVN repository:
https://dist.apache.org/repos/dist/dev/incubator/airflow/Use the dev/airflow-jira script to generate a list of Airflow JIRAs that were closed in the release.
Send out a vote to the dev@airflow.incubator.apache.org mailing list:
Once the vote has been passed, you will need to send a result vote to dev@airflow.incubator.apache.org:
And you will also need to send a vote request to general@incubator.apache.org:
Lastly, you'll need to send the general@ vote result to both general@incubator.apache.org and dev@airflow.incubator.apache.org:
Publishing release
- After both votes pass (see above), you need to migrate the RC artifacts that passed to this repository:
https://dist.apache.org/repos/dist/release/incubator/airflow/
(The migration should including renaming the files so that they no longer have the RC number in their filenames.)
Publishing to PyPi
Create a ~/.pypirc file:
$ cat ~/.pypirc [distutils] index-servers = pypi pypitest [pypi] username=your-username password=********* [pypitest] repository=https://test.pypi.org/legacy/ username=your-username password=*********
(more details here.)
Set proper permissions for the pypirc file:
$ chmod 600 ~/.pypirc
- Confirm that airflow/version.py is set properly.
Install the package in PyPi's test environment:
$ python setup.py sdist upload -r pypitest
- 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 Install the package in PyPi's production environment:
$ python setup.py sdist upload -r pypi
Again, confirm that the package is available here:
https://pypi.python.org/pypi/apache-airflow
Updating CHANGELOG.md
Get a diff between the last version and the current version:
$ git log 1.8.0..1.9.0 --pretty=oneline
- Update CHANGELOG.md with the details, and commit it.
Notifying developers of release
Notify dev@airflow.incubator.apache.org that the artifacts have been published:
Update the Annouce page on the wiki
Publishing documentation
- Follow instructions on Building and deploying the docs
Bulk migrate JIRAs
- Create a release in Jira, and mark as released:
https://issues.apache.org/jira/projects/AIRFLOW?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=released-unreleased
If it gives you the option to move un-resolved issues then move them to the next unreleased version of Airflow
- Otherwise go to the Apache JIRA, and filter for all open/in progress JIRAs for the version that you just released:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20AIRFLOW%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20%3D%201.9.0 - Do a bulk edit to migrate the fix version to the next unreleased version of Airflow.
Old stuff that doesn't apply anymore