Hey Kaival, Thanks for getting this discussion started and offering to RM! I'll go ahead and do it, as I will have the permissions needed.
I'm going to do a branch cut today or tomorrow, and then we will get an RC out early next week, which should give people time to get back and settled after CoC. - Houston On Tue, Oct 6, 2026 at 12:22 AM Kaival Parikh <[email protected]> wrote: > Hi all, > > Thank you for tagging issues and PRs with the 10.6 milestone ( > https://github.com/apache/lucene/milestone/37). > > A few of those are still open, please respond if you'd like to get > something in. > > Any opinions on when to cut the 10.6 branch? Community Over Code is > happening from Oct 11-14, and many people might be busy there (i.e. should > we do it this week: say 10/08, or after the event: say 10/15) > > Also: I realize I'll need help for some parts of the release (like > publishing artifacts, I don't have sufficient permissions), please feel > free to takeover if you're interested and / or think it'll be easier. > > - Kaival > > On 2026-09-29 20:11 UTC Kaival Parikh wrote: > > Hi, > > > > It has been a few months since the 10.5 release, and the changelog for > 10.6 is pretty large now! > > > > There's an ongoing discussion about a Lucene 11 major release in the > mailing list, and based on a suggestion in the same thread: proposing the > next minor release 10.6 (and hopefully the last in the 10.x series!) > > > > I currently see some open PRs and no open issues with the 10.6 > milestone. If you'd like to add something, please open PRs and/or add the > milestone! > > > > I'm happy to be the RM, unless someone else wants to. If there's > consensus, I can start the release process early next week. > > > > - Kaival > > > > --------------------------------------------------------------------- > > 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] > >
