Hi Kaxil, +1 binding. With the assumption that AIP-80 was voted I assume we planned to introduce the new templating early. This would be (in my eyes except we see other things we need to mark deprecated to need to add features for migration preparation) the demand for Airflow 2.11
Jens Sent from Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: Kaxil Naik <kaxiln...@gmail.com> Sent: Thursday, September 5, 2024 3:07:12 AM To: dev@airflow.apache.org <dev@airflow.apache.org> Subject: [VOTE] Airflow 2.11 as bridge release Hi all, As discussed in https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2F7jf12p2mk0nr5495f26r67gnpm3jq8oj&data=05%7C02%7CJens.Scheffler%40de.bosch.com%7C623825ced3b1402f128f08dccd477b5c%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C638610954111360904%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=73VEeNuUBzBonqcfFp9OAriXcUff6HF1BAB%2BMlRwnac%3D&reserved=0<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
