I am happy to be release manager as well. Besides the 30+ PRs marked with milestone 11, there's also 8 open issues. Also, I am not sure how consistently milestones are used. Ideally we'd give folks some time (e.g. 2/3 weeks) to come forward with changes they'd like to get in, which make sense to merge before a release branch is cut. We'd then come up with a plan and some rough timeline for feature freeze and release? This has worked well with Lucene 10 and helped make it a success.
I have two changes in mind that I'd like to work on: - complete the work needed to finally remove search(Query, Collector): https://github.com/apache/lucene/issues/12892 - discuss lowering min supported major version to 9 in main: https://github.com/apache/lucene/pull/16741 - this ties to the existing issue marked with milestone 11 "Relax Lucene Index Upgrade Policy to Allow Safe Upgrades Across Multiple Major Versions" (https://github.com/apache/lucene/issues/13797), which could probably be closed at this point given its corresponding PR is merged, and its followup would be my open PR. I just created a 12 milestone on github and moved https://github.com/apache/lucene/issues/11523 to it. I think moving to 12 is better than untagging, so we don't lose track of these issues in the future. Cheers Luca On Mon, Sep 28, 2026 at 11:16 PM Michael Sokolov via dev <[email protected]> wrote: > > I'd like to restart the release thread. Kaival, I think you had volunteered > to be a RM? But we need to figure out what to include. Things are moving > pretty fast at the moment, it seems to me from the mailing list anyway. But > it's a little hard to see which issues are close and should be included. > There are 32 open PR's tagged with milestone=11.0; however all but two are > marked "Stale". I think we should ignore the Stale ones by default. Of the > two other ones: one is https://github.com/apache/lucene/pull/16034, which > really should be marked Stale since nobody has commented since May (and it > makes me doubt the Stale tagging, actually). So this list may not indicate > the issues folks truly want to get target for 11.0. > > I want to suggest that we go through and "untag" all the issues marked with > 11.0 and have a period of a couple of days where committers can tag issues > they want to see included. Other contributors should please refrain, but feel > free to start a discussion on the mailing list if there is an open issue > under active development that you feel is worth holding a release up for. If > that makes sense, I can do the untagging. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
