You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Kaxil Naik <ka...@gmail.com> on 2024/08/19 12:22:24 UTC
[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 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
Re: [DISCUSS] Airflow 2.11 as bridge release
Posted by "Oliveira, Niko" <on...@amazon.com.INVALID>.
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 <am...@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 <ep...@gmail.com>
wrote:
> +1
>
> On Tue, 20 Aug 2024 at 06:40, Utkarsh Sharma
> <ut...@astronomer.io.invalid> wrote:
>
> > +1 non binding
> >
> > Thanks,
> > Utkarsh Sharma
> >
> > On Tue, Aug 20, 2024 at 10:58 AM Elad Kalif <el...@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.chilukoori@gmail.com>
> > > wrote:
> > >
> > > > +1 non binding.
> > > >
> > > > --
> > > > Regards,
> > > > Vishnu Chilukoori
> > > >
> > > > On Mon, Aug 19, 2024 at 6:40 PM Vikram Koka
> > <vikram@astronomer.io.invalid
> > > >
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Vikram
> > > > >
> > > > >
> > > > > On Mon, Aug 19, 2024 at 12:36 PM Mehta, Shubham
> > > > <shubhx@amazon.com.invalid
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > Shubham
> > > > > >
> > > > > > On 2024-08-19, 11:22 AM, "Michał Modras"
> > > <michalmodras@google.com.INVA
> > > > > > <ma...@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.rx@gmail.com
> > > <mailto:
> > > > > > weilee.rx@gmail.com>> wrote:
> > > > > >
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > Best,
> > > > > > > Wei
> > > > > > >
> > > > > > > > On Aug 19, 2024, at 9:59 PM, Pierre Jeambrun <
> > > > pierrejbrun@gmail.com
> > > > > > <ma...@gmail.com>>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > > On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham <
> > > > > > jedcunningham@apache.org <ma...@apache.org>
> > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >> +1
> > > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > <mailto:
> > > > > > dev-unsubscribe@airflow.apache.org>
> > > > > > > For additional commands, e-mail: dev-help@airflow.apache.org
> > > > <mailto:
> > > > > > dev-help@airflow.apache.org>
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > > > > For additional commands, e-mail: dev-help@airflow.apache.org
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Airflow 2.11 as bridge release
Posted by Amogh Desai <am...@gmail.com>.
+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 <ep...@gmail.com>
wrote:
> +1
>
> On Tue, 20 Aug 2024 at 06:40, Utkarsh Sharma
> <ut...@astronomer.io.invalid> wrote:
>
> > +1 non binding
> >
> > Thanks,
> > Utkarsh Sharma
> >
> > On Tue, Aug 20, 2024 at 10:58 AM Elad Kalif <el...@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.chilukoori@gmail.com>
> > > wrote:
> > >
> > > > +1 non binding.
> > > >
> > > > --
> > > > Regards,
> > > > Vishnu Chilukoori
> > > >
> > > > On Mon, Aug 19, 2024 at 6:40 PM Vikram Koka
> > <vikram@astronomer.io.invalid
> > > >
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Vikram
> > > > >
> > > > >
> > > > > On Mon, Aug 19, 2024 at 12:36 PM Mehta, Shubham
> > > > <shubhx@amazon.com.invalid
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > Shubham
> > > > > >
> > > > > > On 2024-08-19, 11:22 AM, "Michał Modras"
> > > <michalmodras@google.com.INVA
> > > > > > <ma...@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.rx@gmail.com
> > > <mailto:
> > > > > > weilee.rx@gmail.com>> wrote:
> > > > > >
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > Best,
> > > > > > > Wei
> > > > > > >
> > > > > > > > On Aug 19, 2024, at 9:59 PM, Pierre Jeambrun <
> > > > pierrejbrun@gmail.com
> > > > > > <ma...@gmail.com>>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > > On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham <
> > > > > > jedcunningham@apache.org <ma...@apache.org>
> > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >> +1
> > > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > <mailto:
> > > > > > dev-unsubscribe@airflow.apache.org>
> > > > > > > For additional commands, e-mail: dev-help@airflow.apache.org
> > > > <mailto:
> > > > > > dev-help@airflow.apache.org>
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > > > > For additional commands, e-mail: dev-help@airflow.apache.org
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Airflow 2.11 as bridge release
Posted by Ephraim Anierobi <ep...@gmail.com>.
+1
On Tue, 20 Aug 2024 at 06:40, Utkarsh Sharma
<ut...@astronomer.io.invalid> wrote:
> +1 non binding
>
> Thanks,
> Utkarsh Sharma
>
> On Tue, Aug 20, 2024 at 10:58 AM Elad Kalif <el...@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.chilukoori@gmail.com>
> > wrote:
> >
> > > +1 non binding.
> > >
> > > --
> > > Regards,
> > > Vishnu Chilukoori
> > >
> > > On Mon, Aug 19, 2024 at 6:40 PM Vikram Koka
> <vikram@astronomer.io.invalid
> > >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Vikram
> > > >
> > > >
> > > > On Mon, Aug 19, 2024 at 12:36 PM Mehta, Shubham
> > > <shubhx@amazon.com.invalid
> > > > >
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Shubham
> > > > >
> > > > > On 2024-08-19, 11:22 AM, "Michał Modras"
> > <michalmodras@google.com.INVA
> > > > > <ma...@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.rx@gmail.com
> > <mailto:
> > > > > weilee.rx@gmail.com>> wrote:
> > > > >
> > > > >
> > > > > > +1
> > > > > >
> > > > > > Best,
> > > > > > Wei
> > > > > >
> > > > > > > On Aug 19, 2024, at 9:59 PM, Pierre Jeambrun <
> > > pierrejbrun@gmail.com
> > > > > <ma...@gmail.com>>
> > > > > > wrote:
> > > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham <
> > > > > jedcunningham@apache.org <ma...@apache.org>
> > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > >> +1
> > > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > <mailto:
> > > > > dev-unsubscribe@airflow.apache.org>
> > > > > > For additional commands, e-mail: dev-help@airflow.apache.org
> > > <mailto:
> > > > > dev-help@airflow.apache.org>
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > > > For additional commands, e-mail: dev-help@airflow.apache.org
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Airflow 2.11 as bridge release
Posted by Utkarsh Sharma <ut...@astronomer.io.INVALID>.
+1 non binding
Thanks,
Utkarsh Sharma
On Tue, Aug 20, 2024 at 10:58 AM Elad Kalif <el...@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.chilukoori@gmail.com>
> wrote:
>
> > +1 non binding.
> >
> > --
> > Regards,
> > Vishnu Chilukoori
> >
> > On Mon, Aug 19, 2024 at 6:40 PM Vikram Koka <vikram@astronomer.io.invalid
> >
> > wrote:
> >
> > > +1
> > >
> > > Vikram
> > >
> > >
> > > On Mon, Aug 19, 2024 at 12:36 PM Mehta, Shubham
> > <shubhx@amazon.com.invalid
> > > >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Shubham
> > > >
> > > > On 2024-08-19, 11:22 AM, "Michał Modras"
> <michalmodras@google.com.INVA
> > > > <ma...@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.rx@gmail.com
> <mailto:
> > > > weilee.rx@gmail.com>> wrote:
> > > >
> > > >
> > > > > +1
> > > > >
> > > > > Best,
> > > > > Wei
> > > > >
> > > > > > On Aug 19, 2024, at 9:59 PM, Pierre Jeambrun <
> > pierrejbrun@gmail.com
> > > > <ma...@gmail.com>>
> > > > > wrote:
> > > > > >
> > > > > > +1
> > > > > >
> > > > > > On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham <
> > > > jedcunningham@apache.org <ma...@apache.org>
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > >> +1
> > > > > >>
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> <mailto:
> > > > dev-unsubscribe@airflow.apache.org>
> > > > > For additional commands, e-mail: dev-help@airflow.apache.org
> > <mailto:
> > > > dev-help@airflow.apache.org>
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > > For additional commands, e-mail: dev-help@airflow.apache.org
> > > >
> > >
> >
>
Re: [DISCUSS] Airflow 2.11 as bridge release
Posted by Elad Kalif <el...@apache.org>.
+ 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 <vi...@gmail.com>
wrote:
> +1 non binding.
>
> --
> Regards,
> Vishnu Chilukoori
>
> On Mon, Aug 19, 2024 at 6:40 PM Vikram Koka <vi...@astronomer.io.invalid>
> wrote:
>
> > +1
> >
> > Vikram
> >
> >
> > On Mon, Aug 19, 2024 at 12:36 PM Mehta, Shubham
> <shubhx@amazon.com.invalid
> > >
> > wrote:
> >
> > > +1
> > >
> > > Shubham
> > >
> > > On 2024-08-19, 11:22 AM, "Michał Modras" <michalmodras@google.com.INVA
> > > <ma...@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.rx@gmail.com <mailto:
> > > weilee.rx@gmail.com>> wrote:
> > >
> > >
> > > > +1
> > > >
> > > > Best,
> > > > Wei
> > > >
> > > > > On Aug 19, 2024, at 9:59 PM, Pierre Jeambrun <
> pierrejbrun@gmail.com
> > > <ma...@gmail.com>>
> > > > wrote:
> > > > >
> > > > > +1
> > > > >
> > > > > On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham <
> > > jedcunningham@apache.org <ma...@apache.org>
> > > > >
> > > > > wrote:
> > > > >
> > > > >> +1
> > > > >>
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org <mailto:
> > > dev-unsubscribe@airflow.apache.org>
> > > > For additional commands, e-mail: dev-help@airflow.apache.org
> <mailto:
> > > dev-help@airflow.apache.org>
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > For additional commands, e-mail: dev-help@airflow.apache.org
> > >
> >
>
Re: [DISCUSS] Airflow 2.11 as bridge release
Posted by Vishnu Chilukoori <vi...@gmail.com>.
+1 non binding.
--
Regards,
Vishnu Chilukoori
On Mon, Aug 19, 2024 at 6:40 PM Vikram Koka <vi...@astronomer.io.invalid>
wrote:
> +1
>
> Vikram
>
>
> On Mon, Aug 19, 2024 at 12:36 PM Mehta, Shubham <shubhx@amazon.com.invalid
> >
> wrote:
>
> > +1
> >
> > Shubham
> >
> > On 2024-08-19, 11:22 AM, "Michał Modras" <michalmodras@google.com.INVA
> > <ma...@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.rx@gmail.com <mailto:
> > weilee.rx@gmail.com>> wrote:
> >
> >
> > > +1
> > >
> > > Best,
> > > Wei
> > >
> > > > On Aug 19, 2024, at 9:59 PM, Pierre Jeambrun <pierrejbrun@gmail.com
> > <ma...@gmail.com>>
> > > wrote:
> > > >
> > > > +1
> > > >
> > > > On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham <
> > jedcunningham@apache.org <ma...@apache.org>
> > > >
> > > > wrote:
> > > >
> > > >> +1
> > > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org <mailto:
> > dev-unsubscribe@airflow.apache.org>
> > > For additional commands, e-mail: dev-help@airflow.apache.org <mailto:
> > dev-help@airflow.apache.org>
> > >
> > >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > For additional commands, e-mail: dev-help@airflow.apache.org
> >
>
Re: [DISCUSS] Airflow 2.11 as bridge release
Posted by Vikram Koka <vi...@astronomer.io.INVALID>.
+1
Vikram
On Mon, Aug 19, 2024 at 12:36 PM Mehta, Shubham <sh...@amazon.com.invalid>
wrote:
> +1
>
> Shubham
>
> On 2024-08-19, 11:22 AM, "Michał Modras" <michalmodras@google.com.INVA
> <ma...@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.rx@gmail.com <mailto:
> weilee.rx@gmail.com>> wrote:
>
>
> > +1
> >
> > Best,
> > Wei
> >
> > > On Aug 19, 2024, at 9:59 PM, Pierre Jeambrun <pierrejbrun@gmail.com
> <ma...@gmail.com>>
> > wrote:
> > >
> > > +1
> > >
> > > On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham <
> jedcunningham@apache.org <ma...@apache.org>
> > >
> > > wrote:
> > >
> > >> +1
> > >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org <mailto:
> dev-unsubscribe@airflow.apache.org>
> > For additional commands, e-mail: dev-help@airflow.apache.org <mailto:
> dev-help@airflow.apache.org>
> >
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> For additional commands, e-mail: dev-help@airflow.apache.org
>
Re: [DISCUSS] Airflow 2.11 as bridge release
Posted by "Mehta, Shubham" <sh...@amazon.com.INVALID>.
+1
Shubham
On 2024-08-19, 11:22 AM, "Michał Modras" <michalmodras@google.com.INVA <ma...@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.rx@gmail.com <ma...@gmail.com>> wrote:
> +1
>
> Best,
> Wei
>
> > On Aug 19, 2024, at 9:59 PM, Pierre Jeambrun <pierrejbrun@gmail.com <ma...@gmail.com>>
> wrote:
> >
> > +1
> >
> > On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham <jedcunningham@apache.org <ma...@apache.org>
> >
> > wrote:
> >
> >> +1
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org <ma...@airflow.apache.org>
> For additional commands, e-mail: dev-help@airflow.apache.org <ma...@airflow.apache.org>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
For additional commands, e-mail: dev-help@airflow.apache.org
Re: [DISCUSS] Airflow 2.11 as bridge release
Posted by Michał Modras <mi...@google.com.INVALID>.
+1
On Mon, Aug 19, 2024 at 4:21 PM Wei Lee <we...@gmail.com> wrote:
> +1
>
> Best,
> Wei
>
> > On Aug 19, 2024, at 9:59 PM, Pierre Jeambrun <pi...@gmail.com>
> wrote:
> >
> > +1
> >
> > On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham <jedcunningham@apache.org
> >
> > wrote:
> >
> >> +1
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> For additional commands, e-mail: dev-help@airflow.apache.org
>
>
Re: [DISCUSS] Airflow 2.11 as bridge release
Posted by Wei Lee <we...@gmail.com>.
+1
Best,
Wei
> On Aug 19, 2024, at 9:59 PM, Pierre Jeambrun <pi...@gmail.com> wrote:
>
> +1
>
> On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham <je...@apache.org>
> wrote:
>
>> +1
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
For additional commands, e-mail: dev-help@airflow.apache.org
Re: [DISCUSS] Airflow 2.11 as bridge release
Posted by Pierre Jeambrun <pi...@gmail.com>.
+1
On Mon, Aug 19, 2024 at 3:29 PM Jed Cunningham <je...@apache.org>
wrote:
> +1
>
Re: [DISCUSS] Airflow 2.11 as bridge release
Posted by Jed Cunningham <je...@apache.org>.
+1
Re: [DISCUSS] Airflow 2.11 as bridge release
Posted by Jarek Potiuk <ja...@potiuk.com>.
+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 <ka...@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 <ka...@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
> >
>
Re: [DISCUSS] Airflow 2.11 as bridge release
Posted by Kaxil Naik <ka...@gmail.com>.
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 <ka...@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
>