I started to go through the release process, which has been scripted very clearly by Jan and others, and found Jira-specific steps there. I think the translations to GitHub will be pretty straightforward. One thing is that for JIra, we needed to acquire special permissions in order to be able to add new release versions, but I don't think that is true for GitHub ... Any committer should be able to do that, right?
On Wed, Aug 31, 2022, 8:42 PM Tomoko Uchida <tomoko.uchida.1...@gmail.com> wrote: > Hi Mike, > thanks for your response. > > I'm actually not familiar with the whole release procedure that may be > built on Jira. > I hope other people help to interpret Jira-related things on the way into > the language of GitHub issues. > > Tomoko > > 2022年9月1日(木) 3:40 Michael Sokolov <msoko...@gmail.com>: > >> Thanks for the links, Tomoko. I thought it would be helpful to ask on >> the list in case this new system has not been fully internalized by >> all the developers. And I confess I didn't know about that nice >> milestone view! It makes this very easy, assuming of course that >> everyone follows the guidelines and labels the issues with the >> milestone. >> >> On Wed, Aug 31, 2022 at 11:16 AM Tomoko Uchida >> <tomoko.uchida.1...@gmail.com> wrote: >> > >> > Ok in short, you can find blockers for 9.4.0 here. >> > https://github.com/apache/lucene/milestone/3 >> > >> > If there are other issues/PRs that are still not resolved but planned >> to be delivered in 9.4.0, just set their Milestone as 9.4.0. Then they will >> appear in the list. >> > >> > >> > >> > 2022年9月1日(木) 0:00 Tomoko Uchida <tomoko.uchida.1...@gmail.com>: >> >> >> >> I believe we decided to use GitHub Milestone for release planning and >> I wrote documentation about it. >> >> >> https://github.com/apache/lucene/blob/main/dev-docs/github-issues-howto.md >> >> >> >> Is this unclear to you? >> >> >> >> >> >> 2022年8月31日(水) 23:13 Michael Sokolov <msoko...@gmail.com>: >> >>> >> >>> Hi, I'd like to start the ball rolling for a 9.4.0 release. We don't >> >>> have a large number of things, but there are a few nice high-impact >> >>> changes; see excerpt from CHANGE.txt below. I'll volunteer to be >> >>> release manager. I'd just like to know if anybody has any outstanding >> >>> work that is nearing completion and that they'd like to include, >> >>> and/or if we have any known blocker issues*. >> >>> >> >>> * -- I am having a little trouble searching github for blocker issues. >> >>> I think there may not be any, but I tried >> >>> >> https://github.com/apache/lucene/issues?q=is%3Aissue+is%3Aopen+legacy-jira-priority%5C%3AMajor+ >> >>> to find Major issues, for example, and it seems to only find one Minor >> >>> one? Does anyone have better github-search-fu? >> >>> >> >>> API Changes >> >>> --------------------- >> >>> * LUCENE-10577: Add VectorEncoding to enable byte-encoded HNSW vectors >> >>> (Michael Sokolov, Julie Tibshirani) >> >>> >> >>> New Features >> >>> --------------------- >> >>> * LUCENE-10654: Add new ShapeDocValuesField for LatLonShape and >> >>> XYShape. (Nick Knize) >> >>> >> >>> * LUCENE-10629: Support match set filtering with a query in >> >>> MatchingFacetSetCounts. (Stefan Vodita, Shai Erera) >> >>> >> >>> * LUCENE-10633: SortField#setOptimizeSortWithIndexedData and >> >>> SortField#getOptimizeSortWithIndexedData were introduce to provide >> >>> an option to disable sort optimization for various sort fields. >> >>> (Mayya Sharipova) >> >>> >> >>> Improvements >> >>> --------------------- >> >>> * LUCENE-10592: Build HNSW Graph on indexing. (Mayya Sharipova, Adrien >> >>> Grand, Julie Tibshirani) >> >>> >> >>> * GITHUB#11715: Add Integer awareness to RamUsageEstimator.sizeOf >> (Mike Drob) >> >>> >> >>> Optimizations >> >>> --------------------- >> >>> >> >>> * LUCENE-10661: Reduce memory copy in BytesStore. (luyuncheng) >> >>> >> >>> * GITHUB#1020: Support #scoreSupplier and small optimizations to >> >>> DocValuesRewriteMethod. (Greg Miller) >> >>> >> >>> * LUCENE-10633: Added support for dynamic pruning to queries sorted >> by a string >> >>> field that is indexed with terms and SORTED or SORTED_SET doc >> values. >> >>> (Adrien Grand) >> >>> >> >>> * LUCENE-10627: Using ByteBuffersDataInput reduce memory copy on >> >>> compressing data. (luyuncheng) >> >>> >> >>> * GITHUB#1062: Optimize TermInSetQuery when a term is present that >> >>> matches all docs in a segment. >> >>> (Greg Miller) >> >>> >> >>> --------------------------------------------------------------------- >> >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> >>> For additional commands, e-mail: dev-h...@lucene.apache.org >> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> >>
