One more comment.

I believe one of the slow-downs with testing was that it was a few steps to
install - and taking into account that not all PMCs are actively developing
Airflow they could have refrained from testing it.

But this problem is gone now. If you checkout the latest master, it should
be as easy as running:

./breeze --install-airflow-version 1.10.10rc1 --python 3.6 restart
--backend postgres

For testing in python 2.7 you have to do it form v1-10-test branch (but the
command is the same):

./breeze --install-airflow-version 1.10.10rc1 --python 2.7 restart
--backend mysql

I hope this helps and that we will be able to have more votes more quickly!

J.

On Fri, Apr 3, 2020 at 2:32 PM Kaxil Naik <kaxiln...@gmail.com> wrote:

> Hello Airflow Community,
>
> This is a call for the vote to release Apache Airflow version 1.10.10.
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/airflow/1.10.10rc1/
>
> *apache-airflow-1.10.10rc1-source.tar.gz* is a source release that comes
> with INSTALL instructions.
> *apache-airflow-1.10.10rc1-bin.tar.gz* is the binary Python "sdist"
> release.
>
> Public keys are available at https://www.apache.org/dist/airflow/KEYS
>
> The Change Log for the release:
> https://github.com/apache/airflow/blob/1.10.10rc1/CHANGELOG.txt
>
> The vote will be open until 7 April 2020 12:30 PM UTC or until the
> necessary number of votes is reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Only votes from PMC members are binding, but members of the community are
> encouraged to test the release and vote with "(non-binding)".
>
> Please note that the version number excludes the `rcX` string, so it's now
> simply 1.10.10. This will allow us to rename the artifact without modifying
> the artifact checksums when we actually release.
>
> Thanks,
> Kaxil Naik
>


-- 

Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer

M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>

Reply via email to