Re: [DISCUSS] Airflow 2.11 as bridge release

rg Subject: RE: [EXT] [DISCUSS] Airflow 2.11 as bridge release CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. AVERTISSEMENT: Ce courrier électronique provient d’un ex

Re: [DISCUSS] Airflow 2.11 as bridge release

+1 for this idea but I concur with Elad's thought here Thanks & Regards, Amogh Desai On Tue, Aug 20, 2024 at 1:56 PM Ephraim Anierobi wrote: > +1 > > On Tue, 20 Aug 2024 at 06:40, Utkarsh Sharma > wrote: > > > +1 non binding > > > > Thanks, > > Utkarsh Sharma > > > > On Tue, Aug 20, 2024 at 10

Re: [DISCUSS] Airflow 2.11 as bridge release

+1 On Tue, 20 Aug 2024 at 06:40, Utkarsh Sharma wrote: > +1 non binding > > Thanks, > Utkarsh Sharma > > On Tue, Aug 20, 2024 at 10:58 AM Elad Kalif wrote: > > > + 1 > > but I think we should clarify the mental model of the 2.11 release. > > > > I wouldn't say it will have no features. If there

Re: [DISCUSS] Airflow 2.11 as bridge release

+1 non binding Thanks, Utkarsh Sharma On Tue, Aug 20, 2024 at 10:58 AM Elad Kalif wrote: > + 1 > but I think we should clarify the mental model of the 2.11 release. > > I wouldn't say it will have no features. If there are no features then why > 2.11? it can just be 2.10.x > I rather, we agree

Re: [DISCUSS] Airflow 2.11 as bridge release

+ 1 but I think we should clarify the mental model of the 2.11 release. I wouldn't say it will have no features. If there are no features then why 2.11? it can just be 2.10.x I rather, we agree that it will have features which are relevant for the migration (for example: introduce new settings tha

Re: [DISCUSS] Airflow 2.11 as bridge release

+1 non binding. -- Regards, Vishnu Chilukoori On Mon, Aug 19, 2024 at 6:40 PM Vikram Koka wrote: > +1 > > Vikram > > > On Mon, Aug 19, 2024 at 12:36 PM Mehta, Shubham > > wrote: > > > +1 > > > > Shubham > > > > On 2024-08-19, 11:22 AM, "Michał Modras" > L

Re: [DISCUSS] Airflow 2.11 as bridge release

+1 Vikram On Mon, Aug 19, 2024 at 12:36 PM Mehta, Shubham wrote: > +1 > > Shubham > > On 2024-08-19, 11:22 AM, "Michał Modras" LID> wrote: > > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unle

Re: [DISCUSS] Airflow 2.11 as bridge release

+1 Shubham On 2024-08-19, 11:22 AM, "Michał Modras" mailto:michalmod...@google.com.inva>LID> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. AVERTISSEMENT: Ce

Re: [DISCUSS] Airflow 2.11 as bridge release

+1 On Mon, Aug 19, 2024 at 4:21 PM Wei Lee wrote: > +1 > > Best, > Wei > > > On Aug 19, 2024, at 9:59 PM, Pierre Jeambrun > wrote: > > > > +1 > > > > On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham > > > wrote: > > > >> +1 > >> > > > -

Re: [DISCUSS] Airflow 2.11 as bridge release

+1 Best, Wei > On Aug 19, 2024, at 9:59 PM, Pierre Jeambrun wrote: > > +1 > > On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham > wrote: > >> +1 >> - To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org For additional

Re: [DISCUSS] Airflow 2.11 as bridge release

+1 On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham wrote: > +1 >

Re: [DISCUSS] Airflow 2.11 as bridge release

+1

Re: [DISCUSS] Airflow 2.11 as bridge release

+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 A

Re: [DISCUSS] Airflow 2.11 as bridge release

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 wrote: > Hi team, > > After a discussion on the dev call and with some of you

[DISCUSS] Airflow 2.11 as bridge release

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