Somewhat unorganised thoughts— - Not all people may upgrade to 2.10.1 to receive the deprecation warning so this can be problematic. - 2.11 is probably a version all people should upgrade to (or at least be strongly recommended to), so that is a better target. - The situation here is a bit different from previous releases though. Previously we would merge changes for the next minor release to main, but this is not the case for 2.11 (main is for 3.0). - It also seems unproductive to hold off merging the PR until the 2.10 line is finished? - Maybe the best solution is to merge the PR to v2-10-test now, and release it in *the next 2.x release* (whatever version that is). - This will be in 2.10.1 if that happens, which is fine-ish? - This also forces us to have a 2.11 (even if we have 2.10.1, we need a minor release to cement the deprecation warning’s rollout). I guess that’s the plan all the while anyway? But this is where it becomes a MUST. - We’ll probably discover some more missed deprecations during 3.0 development anyway. It’d not be a bad idea to emit more warnings on the v2 branch and release them in 2.11. - We need to discuss the timing of 2.11 at some point. It can’t be too late (or Airflow 3 adoption will be delayed because people need time to fix things against 2.11), but also not too early because that’s probably the last chance we can add deprecations?
> On 16 Aug 2024, at 04:12, Ephraim Anierobi <ephraimanier...@gmail.com> wrote: > > 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 >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org For additional commands, e-mail: dev-h...@airflow.apache.org
