The Lazy consensus have been reached. The https://github.com/apache/airflow/pull/24680 is merged now and the process we are going to follow regarding releasing currrent and previous version of the providers is described now in https://github.com/apache/airflow/blob/main/README.md#release-process-for-providers
I will follow up with those who wish to contribute their cherry-picks and work out more detailed instructions based on our experiences with cherry-picking bugfixes to Airflow releases. Watch out for the next provider's release. J. On Thu, Jun 30, 2022 at 8:23 AM Jarek Potiuk <ja...@potiuk.com> wrote: > > We had a few more clarifications on the description of the approach. > They do not change the "gist" of the proposal but rather is clearer > description on whys and hows. > Thanks for super-valuable feedback and comments Bas and Shubham. > > Just a reminder current description here - > https://github.com/apache/airflow/pull/24680 > > J > > On Tue, Jun 28, 2022 at 11:12 AM Jarek Potiuk <ja...@potiuk.com> wrote: > > > > First iteration of the description updates after feedback applied: > > > > https://github.com/apache/airflow/pull/24680 > > > > I've added more about who the message is for, some more explanation > > what we want to achieve and what expectations there should be from the > > users and contributors/stakeholders who will be involved in > > cherry-picking. > > > > > > On Mon, Jun 27, 2022 at 4:28 PM Jarek Potiuk <ja...@potiuk.com> wrote: > > > > > > I am calling for a lazy consensus on the provider's "mixed governance" > > > model https://lists.apache.org/thread/6ngq79df7op541gfwntspdtsvzlv1cr6 > > > > > > I opened a very small PR that - very shortly - describes the approach > > > in the "user and stakeholder facing " way - i.e. describe to the user > > > what they can expect and to stakeholders what responsibilities this > > > might bring for new providers for them. > > > > > > PR here: https://github.com/apache/airflow/pull/24680 > > > > > > If there are no objections till Friday 1st of July 4.30 pm CEST, I > > > will merge the PR then (following approval and wording discussion of > > > course) and this should make it possible to unblock some of the new > > > provider's PR discussions. > > > > > > I am also in parallel doing some ground work to make it possible to > > > start the next stage of the provider's discussion - i.e. technically > > > splitting the providers out of airflow "core" to separate repos. This > > > is not something decided how and when exactly, but I think it is > > > pretty close to start preparing AIP and discuss it soon. > > > > > > J
