> Tags seem to exist on the lucene-solr repository ( > https://github.com/apache/lucene-solr) so maybe they were missed from the > migration when we did the Lucene/Solr split? +Dawid Weiss > <dawid.we...@gmail.com> I wonder if you have thoughts on this. >
I don't think anything has been missed. Solr and Lucene had a common git repository up until version 8.8.1 and this tag is reflected in Lucene's now-current git: https://github.com/apache/lucene/tree/releases/lucene-solr/8.8.1 All subsequent releases for the 8.x line have been made from the common repository _after the split_ - these tags only exist back in the common repository, they're not forward-ported to the Lucene-only repository. Those historical tags are there for, well, historical reasons. If you're looking for the exact code commit for 8.11.0, you have to look back at the lucene-solr repository (which is the maintenance for the 8.x line), here: https://github.com/apache/lucene-solr/tree/releases/lucene-solr/8.11.0 Anticipating the question, I don't think it makes sense to forward-port commits from lucene-solr to lucene - this would only create additional confusion as to where the development/ maintenance actually takes place. Dawid > On Tue, Oct 4, 2022 at 7:55 AM Shad Storhaug <s...@shadstorhaug.com> > wrote: > >> I was just conversing with a user who mentioned he was using Lucene >> 8.11.0, but when I checked the repo there is no release with that version, >> it ends at 8.8.1. Then I checked on mvnrepository.com and they do exist: >> https://mvnrepository.com/artifact/org.apache.lucene/lucene-core. >> >> >> >> So what gives? Why were these releases not tagged in the repo? If they >> are tagged using a different format, please let me know what the other >> format is. >> >> >> >> Thanks, >> >> Shad Storhaug (NightOwl888) >> >> Project Chairperson – Apache Lucene.NET >> > > > -- > Adrien >
