Oh, good point - there are a bunch of issues there! (in 10.6.0 milestone). I guess we should go through those as well to determine which will be in scope. Eventually we'll have to just set a deadline, but maybe there are some there we can deprioritize?
On Tue, Sep 29, 2026 at 2:40 PM Kaival Parikh <[email protected]> wrote: > > Thanks for starting this thread! > > I was interested in some vector search features coming out in Lucene 11, and > was also curious about the release process (old thread for Lucene 11: > https://lists.apache.org/thread.html/c8sjqg0t79zzo06j6wj3pvhdlg5wph34) > > I'm also happy to contribute to the release process in any way I can! > > Q: if Lucene 11 is the next release, should we also consider things in > milestone 10.6.0 (https://github.com/apache/lucene/milestone/37)? > > On 2026-09-28 21:15 UTC Michael Sokolov via dev 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
