Page History

This page seeks to describe Airflow's policy for blocking the release of an Airflow version, in particular a new major release.

Time based releases

As Airflow is developed on a time-based release policy, missing or incomplete features will not cause a release to be delayed.  

It follows that features being landed in master should be landed in a way that moves the project forward, ideally be built of smaller parts that are useful and complete in their own right, and not be enabled by default until they are ready for use.

Bugs in Releases

 All bugs are important

It is vital that bugs in Airflow are reported in Jira, and assigned a correct severity.

Regressions

Regressions, that is bugs that are present in new versions of Airflow, in existing features, that are not present in older versions, are very important to the community of Airflow and are addressed as a priority.

...