potiuk commented on code in PR #24680: URL: https://github.com/apache/airflow/pull/24680#discussion_r910026923
########## README.md: ########## @@ -410,6 +410,44 @@ For example this means that by default we upgrade the minimum version of Airflow to 2.3.0 in the first Provider's release after 11th of October 2022 (11th of October 2021 is the date when the first `PATCHLEVEL` of 2.2 (2.2.0) has been released. +Providers are often connected with some stakeholders that are vitally interested in maintaining backwards +compatibilities in their integrations (for example cloud providers, or specific service providers). But, +we are also bound with the [Apache Software Foundation release policy](https://www.apache.org/legal/release-policy.html) +which describes who and how releases the ASF software. The provider's governance model is something we name +"mixed governance" - where we follow the release policies, while the burden of maintaining and testing +the cherry-picked versions is on those who commit to perform the cherry-picks and make PRs to older +branches. + +The "mixed governance" means that: + +* The Airflow Community and release manager still decides when to release those providers. + This is fully managed by the community and the usual release-management process following the + [Apache Software Foundation release policy](https://www.apache.org/legal/release-policy.html) +* The contributors (who might or might not be direct stakeholders in the provider) will carry the burden + of cherry-picking and testing the older versions of providers. + +Usually, we release only the most recent version of the provider and rather aggressively +remove deprecations in "major" versions of the providers, however if there is a contributor willing to +make their effort on cherry-picking and testing the non-breaking changes to a selected previous major branch +of the provider which results in releasing maximum two versions of such provider when we release it: Review Comment: Will do. It's called train of thoughts :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
