I backported https://github.com/apache/lucene/pull/16788 to 10.6, and I’d like to get https://github.com/apache/lucene/pull/16891 in as well. I think we’ll need to get fixes for the docBlock/indexSort issues that Salvatore has identified before we can release too?
> On 22 Oct 2026, at 12:34, Michael Sokolov <[email protected]> wrote: > > I pushed a couple of changes out of 10.6 (changed their milestones to > 11) that did not look ready to me, but I wouldn't object to seeing > them in 10.6 if it can happen soon > > On Thu, Oct 22, 2026 at 3:16 AM Luca Cavanna <[email protected]> wrote: >> >> Sounds like a plan, Houston. >> >> On your question: I added the milestone to some PRs that did not have >> it as a best effort, for tracking purposes. Those looked like changes >> that would be good to have, but we should not block the 10.6 release >> if they don't make it in. >> >> Cheers >> Luca >> >> >> On Wed, Oct 21, 2026 at 7:44 PM Houston Putman <[email protected]> wrote: >>> >>> Both of those are fine with me then Luca, and thanks for volunteering to do >>> them! >>> >>> Maybe move the 10.7 issues to 10.6 and give them a few more days to sort >>> themselves out (since it's obviously going to be longer to get those >>> features than if we were doing a 10.7). >>> And after the release is done, I'll move the open bug fix issues to the >>> newly created 10.6.1 milestone and move all the other open issues to 11.0.0. >>> That way if we need to do an RC2, those issues are still being watched and >>> maybe someone will be able to get them merged by then. >>> >>> Quick question. I notice you added the milestone for some of these. Did you >>> do that with a purpose of having them make the release, or just giving them >>> the next milestone in case they were ready at the time? >>> >>> - Houston >>> >>> On Wed, Oct 21, 2026 at 3:55 AM Michael Sokolov <[email protected]> wrote: >>>> >>>> Weird, I saw two of your emails, Luca, the original and the re send. >>>> >>>> On Wed, Oct 21, 2026, 1:19 AM Luca Cavanna <[email protected]> wrote: >>>>> >>>>> LOL, not sure what happened with my previous email and its background >>>>> :) Let me try that again with plain text. >>>>> >>>>> --------------------------------------------- >>>>> >>>>> Thanks Houston! >>>>> >>>>> Based on parallel conversations about Lucene 11.0, I believe 10.6 will >>>>> be the final 10.x release. >>>>> >>>>> With that, I think we should remove the newly created 10.7 milestone, >>>>> and push those issues to 11.0 instead. Also, to avoid confusion around >>>>> backporting and prevent needless backporting overhead, I think we >>>>> should decommission branch_10x like we did with branch_9x, see >>>>> https://github.com/apache/lucene/tree/branch_9x . >>>>> >>>>> I can take care of both in the coming days if nobody has objections. >>>>> >>>>> Cheers >>>>> Luca >>>>> On Wed, Oct 21, 2026 at 10:13 AM Luca Cavanna <[email protected]> wrote: >>>>>> >>>>>> Thanks Houston! >>>>>> >>>>>> Based on parallel conversations about Lucene 11.0, I believe 10.6 will >>>>>> be the final 10.x release. >>>>>> >>>>>> With that, I think we should remove the newly created 10.7 milestone, >>>>>> and push those issues to 11.0 instead. Also, to avoid confusion around >>>>>> backporting and prevent needless backporting overhead, I think we should >>>>>> decommission branch_10x like we did with branch_9x, see >>>>>> https://github.com/apache/lucene/tree/branch_9x . >>>>>> >>>>>> I can take care of both in the coming days if nobody has objections. >>>>>> >>>>>> Cheers >>>>>> Luca >>>>>> >>>>>> On Tue, Oct 20, 2026, 23:21 Houston Putman <[email protected]> wrote: >>>>>>> >>>>>>> I have also added a draft release notes (no content currently) at >>>>>>> https://cwiki.apache.org/confluence/spaces/LUCENE/pages/451980277/ReleaseNote10_6_0 >>>>>>> >>>>>>> So please add things there if you want them included in the >>>>>>> announcement. >>>>>>> >>>>>>> - Houston >>>>>>> >>>>>>> On Tue, Oct 20, 2026 at 1:50 PM Houston Putman <[email protected]> >>>>>>> wrote: >>>>>>>> >>>>>>>> Ok, I'm going through the list of issues with the 10.6 milestone that >>>>>>>> haven't been merged and two are outstanding. >>>>>>>> I'm going to move the milestones of both (#16623 and #16576), since no >>>>>>>> one has made a fuss on them since I announced the feature freeze last >>>>>>>> week. >>>>>>>> Please let me know now if they will land in the next few days. >>>>>>>> >>>>>>>> Other than that, there are a few issues/prs missing backports from >>>>>>>> main that were tagged 10.6 in the changelog. >>>>>>>> I'm tracking those down, and will get them resolved before making the >>>>>>>> RC. >>>>>>>> >>>>>>>> - Houston >>>>>>>> >>>>>>>> On Wed, Oct 14, 2026 at 11:00 AM Houston Putman <[email protected]> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> NOTICE: >>>>>>>>> >>>>>>>>> Branch branch_10_6 has been cut and versions updated to 10.7 on >>>>>>>>> stable branch. >>>>>>>>> >>>>>>>>> Please observe the normal rules: >>>>>>>>> >>>>>>>>> * No new features may be committed to the branch. >>>>>>>>> * Documentation patches, build patches and serious bug fixes may be >>>>>>>>> committed to the branch. However, you should submit all patches you >>>>>>>>> want to commit as pull requests first to give others the chance to >>>>>>>>> review >>>>>>>>> and possibly vote against them. Keep in mind that it is our >>>>>>>>> main intention to keep the branch as stable as possible. >>>>>>>>> * All patches that are intended for the branch should first be >>>>>>>>> committed >>>>>>>>> to the unstable branch, merged into the stable branch, and then into >>>>>>>>> the current release branch. >>>>>>>>> * Normal unstable and stable branch development may continue as usual. >>>>>>>>> However, if you plan to commit a big change to the unstable branch >>>>>>>>> while the branch feature freeze is in effect, think twice: can't the >>>>>>>>> addition wait a couple more days? Merges of bug fixes into the branch >>>>>>>>> may become more difficult. >>>>>>>>> * Only Github issues with Milestone 10.6 >>>>>>>>> will delay a release candidate build. >>>>>>>>> >>>>>>>>> I plan to make an RC on 10/20. So please let me know if any of the >>>>>>>>> remaining open issues in the 10.6.0 milestone are blockers, or if >>>>>>>>> there's anything else you need to make it to the branch. >>>>>>>>> >>>>>>>>> - Houston >>>>> >>>>> --------------------------------------------------------------------- >>>>> 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] >
