+1 binding

Checked sigs/sums and diff from rc1. Simple test works too.

On Thu, 11 Mar, 2021 at 12:38, Elad Kalif <[email protected]> wrote:
+ 1 (non-binding)
Verified issue from RC1 is resolved.

On Thu, Mar 11, 2021 at 12:29 AM Kaxil Naik <[email protected] <mailto:[email protected]>> wrote:
Hey all,

This calls for the release of a new dist: *apache-airflow-upgrade-check*,
version 1.3.0. This represents the contents of the airflow/upgrade/
tree (plus a few supporting files) as a separate dist.

This code is based on the v1-10-stable branch, the git tag is <https://github.com/apache/airflow/releases/tag/upgrade-check%2F1.3.0rc2>

This email is calling a vote on the release, which will last until _*Saturday 13th March 22:30 UTC*_

Consider this my (binding) +1.

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

- *apache-airflow-upgrade-check-1.3.0rc2-source.tar.gz* is a source
release containing the files that made up the binary and wheel
releases.
- *apache-airflow-upgrade-check-1.3.0rc2-bin.tar.gz* is the binary
Python "sdist" release.
- *apache_airflow_upgrade_check-1.3.0rc2-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 on PyPI
<https://pypi.org/project/apache-airflow-upgrade-check/>

*Changelog: *<https://github.com/apache/airflow/tree/upgrade-check/1.3.0rc2/airflow/upgrade#changelog>

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_RELEASE_AIRFLOW.md#verify-release-candidates-by-contributors>>,
but again, this time it is a little bit different.

To actually use this command you will need apache-airflow 1.10.14

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

Thanks,
Kaxil

Reply via email to