+1 (binding): Tested SHA/signature/licences. Installed on top of
Airflow 1.10.5 and saw the new checks running.


On Tue, Jun 15, 2021 at 8:51 PM Kaxil Naik <[email protected]> wrote:
>
> Hey all,
>
> This calls for the release of a: apache-airflow-upgrade-check,
> version 1.4.0. This represents the contents of the airflow/upgrade/
> tree (plus a few supporting files) as a separate dist. This will be the
> last released version of Airflow Upgrade Check before Airflow 1.10.x EOL on 
> 17 June.
>
> This code is based on the v1-10-stable branch, the git tag is 
> https://github.com/apache/airflow/releases/tag/upgrade-check%2F1.4.0rc1
>
> This email is calling a vote on the release, which will last until Friday 
> 18th June 18:50 UTC
>
> Consider this my (binding) +1.
>
> The files can be downloaded from 
> https://dist.apache.org/repos/dist/dev/airflow/upgrade-check/1.4.0rc1/
>
> - apache-airflow-upgrade-check-1.4.0-source.tar.gz is a source
> release containing the files that made up the binary and wheel
> releases.
> - apache-airflow-upgrade-check-1.4.0-bin.tar.gz is the binary
> Python "sdist" release.
> - apache_airflow_upgrade_check-1.4.0-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.4.0rc1/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/main/dev/README_RELEASE_AIRFLOW_UPGRADE_CHECK.md#verify-release-candidates-by-contributors>.
>
> To actually use this command you will need apache-airflow 1.10.15
>
> 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



-- 
+48 660 796 129

Reply via email to