github-actions[bot]andJarek Potiuk
206d9ac9ec
* [main] CI: Upgrade important CI environment * Fix doctoc v2.4.0 duplicate-warning regression doctoc v2.4.0 duplicates the "DON'T EDIT THIS SECTION" warning line on every run when a file has no title between the header comments and the TOC (thlorenz/doctoc#340). Three files in the repo used that pattern, so the hook was adding a stray comment line each time. Add an explicit **Table of contents** title to those three files, which is the shape the 46 other doctoc-managed files in the repo already use. doctoc now leaves them alone on re-run. --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
3.2 KiB
Table of contents
- Adding a Committer or PMC Member
- Airflow Improvement Proposals (AIPs)
- Support for Airflow 1.10.x releases
- Support for Backport Providers
- Release Guidelines
This document describes all the guidelines that have been agreed upon by the committers and PMC members on the mailing list.
Adding a Committer or PMC Member
COMMITTERS.rst contains the guidelines for adding a new Committer and promoting an existing Committer to a PMC member.
Airflow Improvement Proposals (AIPs)
When voting on AIPs, both PMC members and committers have a binding vote. (Link)
Support for Airflow 1.10.x releases
The Airflow 1.10.x series will be supported for six months (June 17, 2021) from Airflow 2.0.0 release date (Dec 17, 2020). Specifically, only 'critical fixes' defined as fixes to bugs that take down Production systems, will be backported to 1.10.x until June 17, 2021.
Support for Backport Providers
Backport providers within 1.10.x, are not released any more, as of (March 17, 2021).
Release Guidelines
Apache Airflow (core)
- Follow Semantic Versioning (SEMVER)
- Changing the version of dependency should not count as breaking change
Providers
Batch & Ad-hoc Releases
- Release Manager would default to releasing Providers in Batch
- If there is a critical bug that needs fixing in a single provider, an ad-hoc release for that provider will be created
Frequency
We will release all providers every month (Mostly first week of the month)
Note: that it generally takes around a week for the vote to pass even though we have 72 hours minimum period
Doc-only changes
When provider(s) has doc-only changes during batch-release, we will not release that provider with a new version. As unliked the actual releases, our doc releases are mutable.
So, we will simply tag that those providers with *-doc1, *-doc2 tags in the repo
to release docs for it.