Re: [VOTE] Release Airflow 2.0.0 from 2.0.0rc1

An emphatic (non-binding) +1 !!! On Wed, Dec 9, 2020 at 8:58 AM Ash Berlin-Taylor wrote: > Hi my lovely Airflowers, > > I have cut Airflow 2.0.0 RC1. This email is calling a vote on the release, > which will run for five days, until 2020-12-14T17:00:00Z > https://www.timeanddate.com/worldclock/f

[VOTE] Bulk release provider packages 1.0.0 form 1.0.0rc1

HI all, To go alongside the vote for releasing apache-airflow-providers-* 1.0.0 from rc1, this email calls for the vote on the provider packages, all 61 of them. The vote which will run for four and a half days, until 2020-12-14T10:00:00Z

Re: [VOTE] Release Airflow 2.0.0 from 2.0.0rc1

Ash is going to also release providers rc1 soon, but for those who would like to test using Docker images. 2.0.0rc1 images are ready with a subset of providers baked in: docker run -it apache/airflow:2.0.0rc1-python3.6 bash airflow@a4726a32f5f3:/opt/airflow$ airflow version 2.0.0 airflow@a4726a32f

[VOTE] Release Airflow 2.0.0 from 2.0.0rc1

Hi my lovely Airflowers, I have cut Airflow 2.0.0 RC1. This email is calling a vote on the release, which will run for five days, until 2020-12-14T17:00:00Z (or until 3 +1 binding votes have been recieved)

Re: Reaching Out actively with 2.0.0 rc(1) to wider community ?

Yeah. I'd probably leave it to the first 2.0.0 release. I think we have a little less stakes there and upgrading PIP is quite a bit easier (and in many cases automated). So reaching out immediately at the 2.0.0 release is probably better idea. I think we can coordinate it and knowing that release

Re: Reaching Out actively with 2.0.0 rc(1) to wider community ?

Tough one. Yes, this is a good idea, but it does possible skirt the apache rules about snapshots/rcs only being for "members of the dev community" or what ever the phrasing is. On Wed, 9 Dec, 2020 at 15:14, Jarek Potiuk wrote: Hello everyone, One thing that I've learned from the recent PI

Reaching Out actively with 2.0.0 rc(1) to wider community ?

Hello everyone, One thing that I've learned from the recent PIP release is that there is never enough reaching out when you publish a new release. I thought of what we can do additionally to all the social/slack/devlist messages and talks and I think with the Airflow Summit/Meetups we have a grea