If there are no features, why wouldn't we follow semver here and release 2.10.x?
On Wed, Sep 4, 2024 at 9:07 PM Kaxil Naik <kaxiln...@gmail.com> wrote: > Hi all, > > As discussed in > https://lists.apache.org/thread/7jf12p2mk0nr5495f26r67gnpm3jq8oj I am > calling for a lazy consensus on using marking 2.11 as a bridge release with > the following ideas: > > > 1. It would only have bug fixes & deprecation warnings as a BRIDGE > release -- NO features. The exception is when adding something to aid > Airflow 2 to 3 migration, for which there can be an explicit mailing > list > discussion > 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. > > > The vote will be closed on Sun, 8th of Sep 2024, 3 am BST. > > Everyone is encouraged to vote, although only PMC members and Committer's > votes are considered binding. > > This is my +1. > > Regards, > Kaxil >
