6 Jan 2021

Attendees

Summary

• Airflow 2.0.1 / Open Issue from 2.0:
  • Milestone: Airflow 2.0.1 Milestone · GitHub
  • Add ‘priority’ labels to all the open issues in 2.0.1 Milestone
  • Release 2.0.1 as soon as the reported bugs are fixed
  • Positive feedback from Scribd – Going PROD with 2.0 in 2 weeks. No major bugs reported by Astronomer, Google / Polidea and Amazon.
• Upgrade Checks
  • Release 1.2.0 soon with a fix for https://github.com/apache/airflow/issues/13293
  • Add a Rule to Check version of Database (MySQL / Postgres / SQLite)
• Providers
  • Elasticsearch and Google (breaking change - 2.0.0) providers would be released soon or at least RCs would be cut next week
• Release Process - Semantic Versioning
  • Changing the version of dependency should not count as breaking change.
  • Ash is working on the doc which will be PRd to Airflow soon
  • Still no unanimous agreement on whether "Major Version should contain new features or just removal of deprecation"
  • Highlight this process to all the committers (chances are some committers are not regularly active). The most important one is that we will strictly follow SEMVER.
• Airflow 2.1 - cadence, candidates and planning
  • Patch releases 2-3 weeks (Might be driven by the bugs and their severity)
  • Minor releases would be released every two months
  • No cadence for Major releases!
  • What happens to the PR that introduces breaking changes??
  • We should not merge that PR until it is a breaking change, instead we should make the PR backwards compatible
  • Or wait until next major release (assign appropriate Github Milestone)