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 > <https://github.com/apache/lucene/pull/16623> and #16576 > <https://github.com/apache/lucene/pull/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 >> >
