Hi,

we discussed the tagging already on Slack. That was exactly Jan's and my 
proposal. Can be scripted.

This should mainly done for branches that are definitely outdated. We can for 
example script this after creating a list of branches that should be removed. 
We won't loose history, because we have all references still in the repo, we 
just want to get rid of those to prevent people from doing wrong things: E.g., 
somebody gets low sugar status and does not know which origin to push to. A 
"not found" error is better than no longer knowing if branch_8x should live on 
repo "a" or repo "b"! In addition, if branch does not exist, wrongly configured 
jenkins jobs wont run!

BTW, we did the same with old branches and tags after the switched from 
subversion to git. Branches are no longer there, but we still have tags under 
"history/".

FYI, I purged the "master" branch in the new repos after INFRA changed the HEAD 
on github and gitbox. If somebody clones our (new) repos, heshe get's "main" by 
default. Thanks to Infra for manually changing the "HEAD" link on the bare 
gitbox and Github repos (which survives also branch deletes and would have been 
detached after master was nuked).

-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: [email protected]

> -----Original Message-----
> From: Dawid Weiss <[email protected]>
> Sent: Wednesday, March 10, 2021 8:13 PM
> To: Lucene Dev <[email protected]>
> Subject: Branch cleaning/ archiving
> 
> I know Uwe wants to purge some (or all) of the existing branches...
> I'm not really fond of removing them - this sort of misses the point
> of pushing the full mirror from the old repo.
> 
> I do understand the will to clean up, however... Maybe we can tag all
> existing branches under a common prefix (archive/lucene-solr/*) and
> then delete those branch refs? Would this be fine, Uwe?
> 
> Dawid
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to