I thought we had a consensus here in terms of being able to have another 5x release if someone felt the need and volunteered but I guess that wasn't the case. I say that because I just saw the following line in the release notes for 5.5:
"This is expected to be the last 5.x feature release before Solr 6.0.0." If everyone else also thinks that it would have not been reasonable to leave a possibility of another 5x release, I'm fine. We might have to evaluate it *if* we get to that bridge though. On Sat, Feb 20, 2016 at 3:10 PM, Noble Paul <noble.p...@gmail.com> wrote: > Yeah, please don't remove it. Let it be there. > On Feb 21, 2016 01:02, "Uwe Schindler" <u...@thetaphi.de> wrote: > >> Hi, >> >> Let's keep the branch. The other ones from 3 and 4 are also still there. >> >> If anybody commits, who cares? If we don't release, it's just useless >> work. >> >> If we want to nuke branch, do the same for previous ones. >> >> Uwe >> >> Am 20. Februar 2016 19:58:21 MEZ, schrieb Dawid Weiss < >> dawid.we...@gmail.com>: >>> >>> Can't we tag it and then delete the branch? >>>> >>> >>> Any reference. So yes, sure you can. But this doesn't really address >>> the second part of my e-mail -- people would still have to issue: >>> >>> git remote prune origin >>> >>> and I don't want to fight Uwe over supposedly magical git commands :) >>> >>> if infra let's us put in any git hooks and protect branches from there. >>>> >>> >>> Yes, this would be another option (but it requires admin-side tweaks). >>> >>> I'm not convinced we need a new strategy just because we are on git though. >>>> We generally don't decide >>>> we won't do a release, someone volunteers to put >>>> one together when something prompts it. I don't remember protecting >>>> branches >>>> in SVN and so I wonder if we need to now? >>>> >>> >>> Exactly. We really don't need to do anything other than just agree to >>> not commit there... that's part of the reason I wanted more "semantic" >>> names for branches -- they're kind of hard to eradicate once created >>> in public. >>> >>> Anyway, as for branch_5x -- no need to protect anything, really. If >>> somebody DOES commit something (by accident or otherwise) we can >>> always revert those commits (or even force the reference to what it >>> was before the mistake, effectively undoing the change). >>> >>> D. >>> >>> ------------------------------ >>> >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >>> For additional commands, e-mail: dev-h...@lucene.apache.org >>> >>> >> -- >> Uwe Schindler >> H.-H.-Meier-Allee 63, 28213 Bremen >> http://www.thetaphi.de >> > -- Anshum Gupta
