Hello Airflow Community,

The vote to release Apache Airflow Upgrade Check 1.2.0 based on 1.2.0rc1 is
now closed.

The vote PASSED with 3 binding "+1", 3 non-binding "+1" and 0 "-1" votes:

3 "+1" binding votes received:
- Kaxil Naik
- Jarek Potiuk
- Xiaodong Deng

"+1" non-Binding votes:
- Dennis Akpenyi
- Ephraim Anierobi
- Vikram Koka

Vote thread:
https://lists.apache.org/thread.html/rb45d7f6f8befbfd0cfb5562e8ee1115cc82b87c39c56297765856802%40%3Cdev.airflow.apache.org%3E

I'll continue with the release process and the release announcement will
follow shortly.

Regards,
Kaxil

On Fri, Feb 12, 2021 at 9:48 PM Vikram Koka <[email protected]>
wrote:

> +1 (non-binding)
>
> Tested locally and with the config file option to skip some builtin
> checks.
>
>
> On Fri, Feb 12, 2021 at 6:13 AM Xiaodong Deng <[email protected]> wrote:
>
>> +1 (binding)
>>
>> On Fri, Feb 12, 2021 at 2:09 PM Jarek Potiuk <[email protected]> wrote:
>>
>>> +1 (binding)
>>>
>>> Verified all sources/signatures/shasums.
>>>
>>> One small comment - the shasum is still in the old form which is not
>>> perfect for verification for some of the installation methods (as discussed
>>> with airflow previously) - might be good to re-generate them in the
>>> "standard" format before moving to release (but it is not a blocker either
>>> way).
>>>
>>> J.
>>>
>>>
>>>
>>> On Fri, Feb 12, 2021 at 1:53 PM Kaxil Naik <[email protected]> wrote:
>>>
>>>> Reminder, I am still waiting for 2 binding votes.
>>>>
>>>> On Thu, Feb 11, 2021, 14:05 Ephraim Anierobi <[email protected]>
>>>> wrote:
>>>>
>>>>> +1(non-binding)
>>>>>
>>>>> On Thu, 11 Feb 2021, 14:07 Dennis Akpenyi, <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> This is my +1
>>>>>>
>>>>>> On 2021/02/09 01:06:54, Kaxil Naik <[email protected]> wrote:
>>>>>> > Hey all,
>>>>>> >
>>>>>> > This calls for the release of a new dist:
>>>>>> *apache-airflow-upgrade-check*,
>>>>>> > version 1.2.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.2.0rc1
>>>>>> >
>>>>>> > This email is calling a vote on the release, which will last until
>>>>>> Friday
>>>>>> > 12th February 01:10 UTC
>>>>>> >
>>>>>> > Consider this my (binding) +1.
>>>>>> >
>>>>>> > The files can be downloaded from
>>>>>> >
>>>>>> https://dist.apache.org/repos/dist/dev/airflow/upgrade-check/1.2.0rc1/
>>>>>> >
>>>>>> > - *apache-airflow-upgrade-check-1.2.0rc1-source.tar.gz* is a source
>>>>>> > release containing the files that made up the binary and wheel
>>>>>> > releases.
>>>>>> > - *apache-airflow-upgrade-check-1.2.0rc1-bin.tar.gz* is the binary
>>>>>> > Python "sdist" release.
>>>>>> > - *apache_airflow_upgrade_check-1.2.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 on PyPI
>>>>>> > https://pypi.org/project/apache-airflow-upgrade-check/
>>>>>> >
>>>>>> > *Changelog: *
>>>>>> >
>>>>>> https://github.com/apache/airflow/tree/upgrade-check/1.2.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/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.2.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