+1. I think that explicit discussion + vote will make it very clear and transparent that no new features will make it to Airflow 2, It will also - as a community decision - make it very easy to say "no" to any new features that people would like to target for Airflow 2 and divert their energy to Airflow 3.
Basically means "Airflow 2 feature freeze now". Full stop. J. On Mon, Aug 19, 2024 at 2:47 PM Kaxil Naik <kaxiln...@gmail.com> wrote: > Once we have an explicit agreement (with a VOTE after this discussion), it > would be added as part of the docs similar to Elad's PR: > https://github.com/apache/airflow/pull/41457 > > On Mon, 19 Aug 2024 at 13:22, Kaxil Naik <kaxiln...@gmail.com> wrote: > > > Hi team, > > > > After a discussion on the dev call and with some of you on various > forums, > > I wanted to propose the following: > > > > 1. It would only have bug fixes & deprecation warnings as a BRIDGE > > release -- NO features > > 2. We would release it after December so Airflow 3.0 features & > > removals are more concrete > > 3. We only release 2.11 if we have to—if most of the things we have > > removed already had deprecation warnings from many minor releases, > then it > > might not be worth it. > > > > > > We can take a call on (3) after Nov-Dec too. > > > > Let me know what you all think. > > > > Regards, > > Kaxil > > >
