Mailing List Archive

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.weiss@gmail.com> I wonder if you have thoughts on this.

On Tue, Oct 4, 2022 at 7:55 AM Shad Storhaug <shad@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

> 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.weiss@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 <shad@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
>

Ahhh thanks Dawid, this makes sense.

On Tue, Oct 4, 2022 at 9:23 AM Dawid Weiss <dawid.weiss@gmail.com> wrote:

>
> 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.weiss@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 <shad@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
>>
>

--
Adrien

Thanks Dawid. I just needed to know where to locate them, so this is fine. I guess I thought the repository moved rather than being cloned, but this makes total sense after you explained it.

From: Adrien Grand <jpountz@gmail.com>
Sent: Tuesday, October 4, 2022 2:25 PM
To: Dawid Weiss <dawid.weiss@gmail.com>
Cc: dev@lucene.apache.org
Subject: Re: Missing tags for releases 8.8.2 thru 8.11.2

Ahhh thanks Dawid, this makes sense.

On Tue, Oct 4, 2022 at 9:23 AM Dawid Weiss <dawid.weiss@gmail.com<mailto:dawid.weiss@gmail.com>> wrote:

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<mailto:dawid.weiss@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 <shad@shadstorhaug.com<mailto:shad@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<http://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


--
Adrien

It was cloned to preserve history (git blame, etc.) but it was decided to
keep 8x development in the shared repo so that the continuity is kept there
(for that major version) rather than in Solr or Lucene after the split.

Dawid

On Tue, Oct 4, 2022 at 11:32 AM Shad Storhaug <shad@shadstorhaug.com> wrote:

> Thanks Dawid. I just needed to know where to locate them, so this is fine.
> I guess I thought the repository moved rather than being cloned, but this
> makes total sense after you explained it.
>
>
>
> *From:* Adrien Grand <jpountz@gmail.com>
> *Sent:* Tuesday, October 4, 2022 2:25 PM
> *To:* Dawid Weiss <dawid.weiss@gmail.com>
> *Cc:* dev@lucene.apache.org
> *Subject:* Re: Missing tags for releases 8.8.2 thru 8.11.2
>
>
>
> Ahhh thanks Dawid, this makes sense.
>
>
>
> On Tue, Oct 4, 2022 at 9:23 AM Dawid Weiss <dawid.weiss@gmail.com> wrote:
>
>
>
> 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.weiss@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 <shad@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
>
>
>
>
> --
>
> Adrien
>