Re: Mirroring the later 8.x release tags in the "new" split repositories

d Weiss > *Sent:* Wednesday, January 5, 2022 8:17 AM > *To:* Lucene Dev > *Cc:* Solr Dev > *Subject:* Re: Mirroring the later 8.x release tags in the "new" split > repositories > > > > > > I did mean that we should be pushing the tags as well as the

RE: Mirroring the later 8.x release tags in the "new" split repositories

nesday, January 5, 2022 8:17 AM To: Lucene Dev Cc: Solr Dev Subject: Re: Mirroring the later 8.x release tags in the "new" split repositories I did mean that we should be pushing the tags as well as their associated commits. You can even edit them by hand so you can

Re: Mirroring the later 8.x release tags in the "new" split repositories

> I did mean that we should be pushing the tags as well as their associated > commits. > You can even edit them by hand so you can definitely have references pointing at void... I already expressed my opinion on the matter but I won't object if you wish to do it. The problem I see is that it's

Re: Mirroring the later 8.x release tags in the "new" split repositories

+1 to Houston's proposal. Given all the release tags seen here: https://github.com/apache/solr/tags it makes sense that it would include the tag for 8.11 and the others we're missing. I think this is a really easy decision as it's weird/inconsistent that these particular versions are omitted yet

Re: Mirroring the later 8.x release tags in the "new" split repositories

Dawid, I did mean that we should be pushing the tags as well as their associated commits. I was unaware that you could push the tags without the commits, sorry if I caused confusion there. Jan, Looking in the diff between the "history/branches/lucene-solr/branch_8x" tag in apache/solr and the

Re: Mirroring the later 8.x release tags in the "new" split repositories

> You can push a tag to a repo that doesn't already have that commit (or > history of commits) in an existing branch, without issue. But why do it? These are refs - if they point to non-existing commits then I honestly don't see any value in having them. It would confuse the hell out of me. >

Re: Mirroring the later 8.x release tags in the "new" split repositories

They don't have those commits, but they also don't have the commits for the previous release tags in the repo. You can go to any of the release tags, choose a commit to view and you will get a message saying: > This commit does not belong to any branch on this repository, > and may belong to a

Re: Mirroring the later 8.x release tags in the "new" split repositories

> As mentioned in SOLR-15874, we are not hosting the tags for the latest 8.x > releases in the split apache/solr and apache/lucene repositories. All release > tags made prior to the repository split exist in the new repos, so I see no > reason that the newer 8.x tags cannot exist in the new

Re: Mirroring the later 8.x release tags in the "new" split repositories

I think mirroring the tags is a good idea and can only be useful. On Tue, Jan 4, 2022 at 8:56 AM Houston Putman wrote: > Hello all, > > As mentioned in SOLR-15874 > , we are not hosting > the tags for the latest 8.x releases in the split

Mirroring the later 8.x release tags in the "new" split repositories

Hello all, As mentioned in SOLR-15874 , we are not hosting the tags for the latest 8.x releases in the split apache/solr and apache/lucene repositories. All release tags made prior to the repository split exist in the new repos, so I see no reason