On 4/5/2019 3:19 AM, Adrien Grand wrote:
Apparently it is possible to ask INFRA to mark branches as
protected[1]. Should we do it for branches that are not expecting new
releases anymore? I think it would make things less trappy. For
instance, backporting to branch_7x is almost for sure a mistake since
we are not going to release lucene/solr 7.8.
[1] https://issues.apache.org/jira/browse/INFRA-18109
What would you think of protecting the following branches:
branch_3x
branch_4x
branch_5_4
branch_5_5
branch_5x
branch_6_0
branch_6_1
branch_6_2
branch_6_3
branch_6_4
branch_6_5
branch_6x
branch_7_0
branch_7_1
branch_7_2
branch_7_3
branch_7_4
branch_7_5
branch_7_6
branch_7x
In the SVN days, branches were simply deleted when we were through
cutting releases from them. Deleted branches all came back when we
converted to git.
Is protecting them the only way to maintain the history? If so, then
I'm +1. Does deleting them like we did on SVN make it impossible to "go
back in time" in the repo?
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
