Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated based on planning meeting on 26 Oct

...

The immediate action items with respect to scope and major milestones are:

  1. Testing of the first second 2.0.0alpha build.
  2. Fix bugs as they are raised with alpha builds.
  3. Bug-fixing and release of the second alpha Cut the beta build.
  4. Documentation for "Getting started with 2.0 and upgrading to 2.0" to enable beta testing. Identify any additional urgent documentation additions needed for the beta testing of the Airflow 2.0 release. , as well as for 2.0 once released. Also, enhance the upgrade check scripts as needed.
  5. Close out release management related open items with respect to release of Providers packages. Not necessarily needed for beta1, but before RC. 

...

DateMilestone
Week of 7 Sep 2020Create the 2.0.0-test branch - Done.

While the scope is fluid, we would be rebasing this test branch from master. After we completely freeze the scope, we would only cherrypick commits from Airflow Master to v2-0-test branch if they are “in-scope”. Normal development would continue on Master branch i.e. PRs would be created against Airflow Master.

Week of 12 Oct 2020

First Airflow 2.0 alpha release "apache-airflow-2.0.0.alpha1 a1" cut on Oct 13th.

Week of 19 26 Oct 2020Cut second alpha releaseSecond Airflow 2.0 alpha release "apache-airflow-2.0.0.a2" cut on Oct 26th.
Week of 26 Oct 2020

Cut first 2.0 beta release. Based on the discussion in the Airflow 2.0 planning meeting, this may be in sync with the bridge release below and may be the first week of November.


Beta snapshots would be published to the Airflow Community to test and create issues to make sure Airflow is functioning and backwards compatible. 

Week of 2 Nov 2020Cut bridge release based on 1.10.x - jump-off point to 2.0. Probably 1.10.13 or 1.10.14 containing upgrade check scripts for 2.0
Week of 9 Nov 2020Cut second 2.0 beta release
Week of 23 Nov 2020Cut third 2.0 beta release
Week of 7 Dec 2020Cut first 2.0 release candidate (2.0.0rc1)

As part of creating the release candidate, an official vote would be started to release 2.0.0. If there are any bugs discovered in 2.0.0rc1, they will be fixed and a new release candidate will be published.  This will be repeated until the Vote passes

...