Update on the Release. I have paused further work on this release until we fully debug this issue: https://github.com/apache/lucene/issues/15662. One suspect is the Linux Kernel update that occurred on the benchmarking machine.
We need to confirm if indeed that is the cause (Mike McCandless is on the case!). If so, I will proceed with the release. Freeze is still in place. Thanks y'all Ben On Tue, Feb 3, 2026 at 9:00 AM Benjamin Trent <[email protected]> wrote: > Hey y'all, > > I have cut the 10.4 branch. I did this and pushed before I saw the > messages in the thread about issue: > https://github.com/apache/lucene/issues/15662 > > I have flagged that issue with Milestone 10.4 as a regression of that > magnitude likely indicates a nasty bug we should fix. > > Regular notice still applies. Only critical bug fixes, and I would say a > regression of almost 2x signifies as critical in this case. > > NOTICE: > > Branch branch_10_4 has been cut and versions updated to 10.5 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.4 > will delay a release candidate build. > ---- >
