Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated based on progress in the last week and planning meeting earlier today.

...

  1. Encourage users to test the beta3 build, especially around Kubernetes.
  2. Continue testing beta builds.
  3. Work on Test the 1.10.13 "bridge release" to cut it and enable migration / upgrade testing.and release it.
  4. Test the upgrade check scripts build and release it.
  5. Continue working Focus on the "Upgrading to 2.0 from 1.10.x" documentation and the upgrade check scripts
  6. Focusing Focus on stability , and critical bug fixes as needed in preparation for Release Candidate builds. 

...

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.a1" cut on Oct 13th.

Week of 26 Oct 2020Second Airflow 2.0 alpha release "apache-airflow-2.0.0.a2" cut on Oct 26th.
Week of 9 Nov 2020

Cut first 2.0 beta release. First beta build cut on Nov 9th.


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

10 Nov  - 7 Dec 

Cut beta releases approximately every Tuesday.

Latest beta build is beta3, cut on Nov 18th and available for testing.

Weeks of 16 Nov and 23 Nov 2020

Cut bridge release based on 1.10.x - jump-off point to 2.0 and submit for vote. Release candidate 1.10.13rc1 submitted for vote on Nov 20th. 

Release the 1.10.13 "bridge release" after vote is concluded. Expected to be the week of 23rd Nov.

Upgrade check scripts released independently. Release candidate of Upgrade check scripts cut and submitted for vote on Nov 20th.

Release the upgrade check scripts after vote is concluded. Expected to be the week of 23rd NovUpgrade check scripts to be released independently, but in the same time frame.

Week of 7 Dec 2020Cut first 2.0 release candidate (2.0.0rc1)

As part of creating the release candidate, an official vote of 3 working days 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.

Approach

In the interest of clarity, the core approach is detailed below:

...