Ok, thank you. Disappearing branches are a bit puzzling if you have a tracking branch locally. For branch_8x, we removed the content and left a note stating what happened:
https://github.com/apache/lucene-solr/tree/branch_8x This still refers to branch_9x, for example. Maybe we should do the same for branch_9x - redirect people to the next major dev branch but leave the label? There are ways of protecting commits to dead branches as well, to prevent accidental commits. Dawid On Thu, Oct 10, 2024 at 12:13 PM Chris Hegarty <christopher.hega...@elastic.co.invalid> wrote: > Hi Dawid, > > > On 10 Oct 2024, at 10:57, Dawid Weiss <dawid.we...@gmail.com> wrote: > > > > > > Hmm... Has someone removed branch_9x entirely from the origin git? > > Yes, that was me, see > https://lists.apache.org/thread/8nvnqm7njjho7df99fjx6dxm4zcr7dhj > > Before removing I checked that there was nothing in that branch that is > not already in branch_9_12. > > > I'd think we'd like to keep the label, even if the branch is not meant > for any future development, similar to branch_8x that still exists in > lucene-solr repo. > > I thought that deleting it was the right thing to do, but we can restore > the label or something if you think that useful? > > -Chris. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
