Hey all,

This vote is a little bit different to our usual ones. This calls for the first release fo apache-airflow-upgrade-check -- a collection of rules to ease the upgrade from 1.10 to 2.0.0. These checks are not final or complete, and more can be released in future releases of this dist, and users will be notified that there is an update available.

This calls for the release of a new dist: apache-airflow-upgrade-check, version 1.0.0. This represents the contents of the airflow/upgrade/ tree (plus a few supporting files) as a separate dist, as called for in <https://github.com/apache/airflow/issues/11112>

This email is calling a vote on the release, which will last until 10:00 UTC on Wednesday 25th November (timed to coincide with the planned 1.10.13rc1 vote)

Consider this my (binding) +1.

The files can be downloaded from
<https://dist.apache.org/repos/dist/dev/airflow/upgrade-check/1.0.0rc1/>

**apache-airflow-upgrade-check-1.0.0rc1-source.tar.gz** is a source release containing the files that made up the binary and wheel releases.

** apache-airflow-upgrade-check-1.0.0rc1-bin.tar.gz** is the binary Python "sdist" release.

** apache_airflow_upgrade_check-1.0.0rc1-py2.py3-none-any.whl** is the binary Python pre-compiled wheel file.

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

This dist is also available PyPI <https://pypi.org/project/apache-airflow-upgrade-check/>

Only votes from PMC members are binding, but members of the community 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/master/dev/README.md#vote-and-verify-the-apache-airflow-release-candidate>, but again, this time it is a little bit different.

To actually use this command, either wait for Kaxil to release the 1.10.13rc1, and then run `airflow upgrade_check`, or in the mean time you can run this with `python -c 'from airflow.upgrade.checker import __main__; __main__()'`

Please note that the version number inside the archives exclude the `rcX` string, so it's now simply 1.0.0. This will allow us to rename the artifact without modifying the artifact checksums when we actually release.

Thanks,
Ash

Reply via email to