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]
