Agree with Elad's take on this. I'd say no "large" features, but leaving some wiggle room for changes that allow an easier segue to Airflow 3 would be great.
________________________________ From: Amogh Desai <amoghdesai....@gmail.com> Sent: Tuesday, August 20, 2024 8:53:21 PM To: dev@airflow.apache.org 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 expéditeur externe. Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que le contenu ne présente aucun risque. +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 <ephraimanier...@gmail.com> wrote: > +1 > > On Tue, 20 Aug 2024 at 06:40, Utkarsh Sharma > <utkarsh.sha...@astronomer.io.invalid> wrote: > > > +1 non binding > > > > Thanks, > > Utkarsh Sharma > > > > On Tue, Aug 20, 2024 at 10:58 AM Elad Kalif <elad...@apache.org> 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 that it will have features which are relevant for > the > > > migration (for example: introduce new settings that we think can make > > > migration easier etc...) > > > We should leave room for exceptions, if a community member thinks that > a > > > specific feature is crucial for 2.x and can not wait for Airflow 3 I > > would > > > rather give them the option to make their case rather than saying no in > > > advance. I suggest that such cases will have a mailing list discussion > / > > > Airflow 3 call discussion and lazy consensus vote. With clarification > > that > > > the technical effort in getting the feature to 2.11 is on the community > > > member who advocated for it. > > > > > > > > > On Tue, Aug 20, 2024 at 6:56 AM Vishnu Chilukoori < > > > vish.chiluko...@gmail.com> > > > wrote: > > > > > > > +1 non binding. > > > > > > > > -- > > > > Regards, > > > > Vishnu Chilukoori > > > > > > > > On Mon, Aug 19, 2024 at 6:40 PM Vikram Koka > > <vik...@astronomer.io.invalid > > > > > > > > wrote: > > > > > > > > > +1 > > > > > > > > > > Vikram > > > > > > > > > > > > > > > On Mon, Aug 19, 2024 at 12:36 PM Mehta, Shubham > > > > <shu...@amazon.com.invalid > > > > > > > > > > > wrote: > > > > > > > > > > > +1 > > > > > > > > > > > > Shubham > > > > > > > > > > > > On 2024-08-19, 11:22 AM, "Michał Modras" > > > <michalmod...@google.com.inva > > > > > > <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 courrier électronique provient d’un expéditeur > > > > externe. > > > > > > Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous > > ne > > > > > pouvez > > > > > > pas confirmer l’identité de l’expéditeur et si vous n’êtes pas > > > certain > > > > > que > > > > > > le contenu ne présente aucun risque. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > > > On Mon, Aug 19, 2024 at 4:21 PM Wei Lee <weilee...@gmail.com > > > <mailto: > > > > > > weilee...@gmail.com>> wrote: > > > > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > Best, > > > > > > > Wei > > > > > > > > > > > > > > > On Aug 19, 2024, at 9:59 PM, Pierre Jeambrun < > > > > pierrejb...@gmail.com > > > > > > <mailto:pierrejb...@gmail.com>> > > > > > > > wrote: > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham < > > > > > > jedcunning...@apache.org <mailto:jedcunning...@apache.org> > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > >> +1 > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > > > <mailto: > > > > > > dev-unsubscr...@airflow.apache.org> > > > > > > > For additional commands, e-mail: dev-h...@airflow.apache.org > > > > <mailto: > > > > > > dev-h...@airflow.apache.org> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > > > > > > For additional commands, e-mail: dev-h...@airflow.apache.org > > > > > > > > > > > > > > > > > > > > >
