I agree with Dawid, why the hell do we need those tags? The old lucene-solr repo can stay forever on Github. If I want to checkout an older version, I would go into the old repo and check it out. In fact that’s also what tools may do, because the old git repo is stated in the pom.xml files (or similar).
I would rather go and nuke the tags (not the commits of course) from new repo for everything before 9. Uwe ----- Uwe Schindler Achterdiek 19, D-28357 Bremen <https://www.thetaphi.de> https://www.thetaphi.de eMail: u...@thetaphi.de From: Dawid Weiss <dawid.we...@gmail.com> Sent: Wednesday, January 5, 2022 8:17 AM To: Lucene Dev <d...@lucene.apache.org> Cc: Solr Dev <dev@solr.apache.org> 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 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 really easy to break things in a catastrophic way by force-pushing refs or by pushing refs that shouldn't be copied - it's not hard, but it's easy to make a mistake. I'd try out ten times on a bare test clone somewhere before actually doing it on the target git repository. But it is definitely doable. Git repositories are conceptually very simple - just a graph of commits and tags/ labels. Dawid
