Hearing no objections, I went ahead with next steps: - created branch_11x - opened a PR to replace all mentions of branch_10x with branch_11x: https://github.com/apache/lucene/pull/16929 - created new jenkins jobs that point to branch_11x - disabled all jenkins jobs that pointed to branch_10x - opened PR to remove 10.7 version from main and branch_11x: https://github.com/apache/lucene/pull/16930 - will open PR to add 12.0 version to main once the previous one to remove 10.7 is merged
@Uwe I believe you'd need to update your builds as well. This should be all we need to do to safely decommission branch_10x (https://github.com/apache/lucene/pull/16911) and not break anything. >From now on, please backport from main into the stable branch_11x instead of branch_10x. It will take some getting used to I suppose :) Let me know if I missed anything Cheers Luca On Mon, Oct 26, 2026 at 5:17 PM Luca Cavanna <[email protected]> wrote: > > Hey all, > branch_10_6 has been created, and the Lucene 10.6 release is ongoing. > > We also discussed releasing Lucene 11, and I volunteered to be its > release manager. > > The plan is for 10.6 to be the last minor release of the 10.x series. > Please let me know if you have concerns or questions about this? > > The next step would be to remove the 10.7 milestone from github and > decommission the branch_10x like we have done with branch_9x in the > past, to prevent unwanted backports and confusion. Here is a PR: > https://github.com/apache/lucene/pull/16911 . I will proceed to create > branch_11x as well. > > I will follow up on the Lucene 11 release thread with outstanding > items and a tentative date proposal for it. > > > Cheers > Luca --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
