Regarding 3.1.9, I agree that we should only be doing it if a bug worthy of it is found and there's no good / reasonable workaround to fix it.
Thanks & Regards, Amogh Desai On Tue, Mar 17, 2026 at 10:24 AM Rahul Vats <[email protected]> wrote: > Hello, > > On 3.1.9: I prefer we only cut 3.1.9 if a critical bug is found in 3.1.8 > before 3.2.0 is released. Otherwise, 3.1.8 can remain the last 3.1.x > release. > On v3-2-test: I don’t think we need cherry-picking to v3-2-test right now. > My plan is to fast-forward v3-2-test from main and only drop features that > are not planned for 3.2. I’ll keep v3-2-test in sync with main. > Happy to discuss this, though. > > Regards, > Rahul Vats > > > On Mon, 16 Mar 2026 at 19:34, Elad Kalif <[email protected]> wrote: > > > Hello, > > > > We need to decide when we will stop cherry picking to v3-1-test and > > starting to cherry pick to v3-2-test. > > Am I correct to assume the plan is to release 3.2 and then right after > > release 3.1.9 which will be the last version in 3.1.x? > > > > > > On Fri, Feb 27, 2026 at 10:12 PM Vincent Beck <[email protected]> > wrote: > > > > > Thanks Vikram > > > > > > On 2026/02/27 20:04:45 Vikram Koka via dev wrote: > > > > Airflow 3.1.8 is planned for the week of March 8 > > > > > > > > On Fri, Feb 27, 2026 at 12:02 PM Vincent Beck <[email protected]> > > > wrote: > > > > > > > > > Kind of related, I can see there are still quite a few PRs to > > backport > > > in > > > > > `v3-1-test`. Are we planning to release another patch version in > 3.1? > > > If > > > > > not, then I think we should remove the backport in 3.1 label. > > > > > > > > > > On 2026/02/27 03:58:00 Rahul Vats wrote: > > > > > > Agreed, Thanks Kaxil. > > > > > > > > > > > > Regards, > > > > > > Rahul Vats > > > > > > > > > > > > On Thu, 26 Feb 2026 at 23:57, Kaxil Naik <[email protected]> > > > wrote: > > > > > > > > > > > > > We don't need to add that label yet, until we have rc1 -- > mostly > > we > > > > > would > > > > > > > be doing fast-forwards only. So for now, don't add that label > to > > > any > > > > > PRs :) > > > > > > > > > > > > > > On Thu, 26 Feb 2026 at 16:10, Vincent Beck < > [email protected]> > > > > > wrote: > > > > > > > > > > > > > > > Thanks Rahul :) > > > > > > > > > > > > > > > > On 2026/02/26 16:00:32 Rahul Vats wrote: > > > > > > > > > Yes, Vincent, I have created the label > backport-to-v3-2-test. > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > Rahul Vats > > > > > > > > > > > > > > > > > > On Thu, 26 Feb 2026 at 21:22, Vincent Beck < > > > [email protected]> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Thanks Rahul for preparing this. Question: should we > > create a > > > > > label > > > > > > > to > > > > > > > > > > easily backport PR to `v3-2-test`? > > > > > > > > > > > > > > > > > > > > On 2026/02/26 14:35:47 Rahul Vats wrote: > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > > > > > > > I’ll be cutting 3.2.0b1 in the next couple of days. > > > > > > > > > > > > > > > > > > > > > > The v3-2-test branch created today and is currently in > > sync > > > > > with > > > > > > > > > > > main. From this point forward, any new features added > to > > > main > > > > > will > > > > > > > > *not* > > > > > > > > > > be > > > > > > > > > > > included in 3.2. Work on existing new feature is fine. > > > "main" > > > > > > > branch > > > > > > > > will > > > > > > > > > > > soon target 3.3. *NO ACTION IS NEEDED* > > > > > > > > > > > from anyone for backporting anything. I'll keep > v3-2-test > > > > > mostly > > > > > > > > in-sync > > > > > > > > > > > with main and remove any PRs/commits that introduce new > > > > > features. > > > > > > > > > > > > > > > > > > > > > > Let’s focus our efforts over the coming days on: > > > > > > > > > > > > > > > > > > > > > > - Prioritizing bugfixes > > > > > > > > > > > - Completing ongoing 3.2 features, including (but > not > > > > > limited > > > > > > > to) > > > > > > > > docs > > > > > > > > > > > coverage > > > > > > > > > > > > > > > > > > > > > > This will help ensure we get a stable and solid release > > > out the > > > > > > > > > > > door, tentatively planned for the end of the month. > > > > > > > > > > > > > > > > > > > > > > Finally, a call for action: I’ll need help with > *release > > > > > notes* & > > > > > > > > > > *release > > > > > > > > > > > blog post* for new features in 3.2. > > > > > > > > > > > > > > > > > > > > > > - If you’ve worked on adding a new feature and would > > > like it > > > > > > > > > > > highlighted, please either let me know or open a PR > > > with a > > > > > > > > detailed > > > > > > > > > > > newsfragment for release notes > > > > > > > > > > > - For the blog post, please also send in your > entries > > - > > > > > > > > screenshots > > > > > > > > > > > would be especially valuable for UI features. > > > > > > > > > > > > > > > > > > > > > > Thanks everyone, for your contributions! > > > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > > Rahul Vats > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > > To unsubscribe, e-mail: > [email protected] > > > > > > > > > > For additional commands, e-mail: > > [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > To unsubscribe, e-mail: [email protected] > > > > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [email protected] > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > >
