+1 (non-binding)

Tested with regular checks and with the --config option to ignore certain
rules.

Vikram


On Fri, Dec 11, 2020 at 6:15 AM Tomasz Urbaszek <tomasz.urbas...@polidea.com>
wrote:

> +1 binding
>
> On Fri, Dec 11, 2020 at 3:05 PM Ash Berlin-Taylor <a...@apache.org> wrote:
>
>> Hey all,
>>
>> This calls for the release of a new dist: apache-airflow-upgrade-check,
>> version 1.1.0. This represents the contents of the airflow/upgrade/
>> tree (plus a few supporting files) as a separate dist This code is based
>> off the v1-10-stable branch, the git tag is
>> https://github.com/apache/airflow/releases/tag/upgrade-check%2F1.1.0rc1
>>
>> This email is calling a vote on the release, which will last until
>> 10:00 UTC on Monday 14th December 14:00 UTC
>>
>> Consider this my (binding) +1.
>>
>> The files can be downloaded from
>> https://dist.apache.org/repos/dist/dev/airflow/upgrade-check/1.1.0rc1/
>>
>> **apache-airflow-upgrade-check-1.1.0rc1-source.tar.gz** is a source
>> release containing the files that made up the binary and wheel
>> releases.
>>
>> ** apache-airflow-upgrade-check-1.1.0rc1-bin.tar.gz** is the binary
>> Python "sdist" release.
>>
>> ** apache_airflow_upgrade_check-1.1.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 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.0.0. This will allow us to rename
>> the artifact without modifying the artifact checksums when we actually
>> release.
>>
>> Thanks,
>> Ash
>>
>
>
> --
>
> Tomasz Urbaszek
> Polidea <https://www.polidea.com/> | Software Engineer
>
> M: +48 505 628 493 <+48505628493>
> E: tomasz.urbas...@polidea.com <tomasz.urbasz...@polidea.com>
>
> Unique Tech
> Check out our projects! <https://www.polidea.com/our-work>
>

Reply via email to