Hi Alex, nice to see you!
On 08/10/2020 04:57, Alexander Shorin wrote:
+1, but...
Old release branches could be just dropped without a worry. If something
there wasn't released since today - well, nobody actually has any need for
it. If someone does - make a release, tag it and drop the branch.
Unexpetable action.
The only release branches I'm proposing to keep are those that are
nominally still active. We haven't officially said that we're done with
2.x releases yet - if you want to propose a VOTE on that, please do so.
3.x and main track active releases. master needs to stay until Paul's
work to replace it with main is done. And I'm not sure everything from
prototype/fdb-layer is in main yet, I'll let active devs on it comment.
The work to add the tags for restoration is optional, but doesn't hurt
anyone.
90 days is quite long. 30 would be more than enough according to actual
activity.
Just an "overabundance of caution" :)
And don't we have a policy that merged branches should be deleted
automatically as well?
Yes, but in certain cases (like nebraska-merge) we've been lenient.
Obviously these can be cleaned up with prejudice.
-Joan
