We can have it in 2.10.1 or 2.11.0 if it can't be in a patch release. On Thu, 15 Aug 2024 at 21:07, Tzu-ping Chung <t...@astronomer.io.invalid> wrote:
> I think this needs to be in Airflow 2 before 3.0 is released so people > actually receive the notification for the breaking change we’re going to > make. > > Assuming this does not make it into 2.10, what is the best option to send > out the deprecation? > > > > On 16 Aug 2024, at 03:36, Ephraim Anierobi <ephraimanier...@gmail.com> > wrote: > > > > Looks like the PR is late. Is it ok if we include it in the next Airflow > 2 > > release? > > > > On Thu, 15 Aug 2024 at 20:29, Tzu-ping Chung <t...@astronomer.io.invalid> > > wrote: > > > >> I think we need to get this backport into 2.10 > >> > >> https://github.com/apache/airflow/pull/41469 > >> > >> > >>> On 16 Aug 2024, at 03:14, Utkarsh Sharma <utkarsh.sha...@astronomer.io > .INVALID> > >> wrote: > >>> > >>> Hello, > >>> > >>> Apache Airflow 2.10.0 (based on RC1) has been accepted. > >>> > >>> 3 "+1" binding votes received: > >>> - Kaxil Naik > >>> - Jed Cunningham > >>> - Ephraim Anierobi > >>> > >>> > >>> 2 "+1" non-binding votes received: > >>> - Rahul Vats > >>> - Utkarsh Sharma > >>> > >>> Vote thread: > >>> https://lists.apache.org/thread/sho6wrdkmtx2vzh18zqxmtw3z897455j > >>> > >>> I'll continue with the release process, and the release announcement > will > >>> follow shortly. > >>> > >>> Cheers, > >>> Utkarsh Sharma > >> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > For additional commands, e-mail: dev-h...@airflow.apache.org > >
