On 2017-03-14 11:59, Michael Dürig wrote:
Hi, Following up on Davide's release plan for Oak 1.6 [1] we should define a merge policy for the 1.6 branch. I would suggest to be a bit more conservative here than we have been in the past and ask for reviews of backports. That is, announce candidates on @oak-dev mentioning the issue reference, potential risks, mitigations, etc. I don't think we need to block the actual backport being performed on the outcome of the review as in the worst case changes can always be reverted. The main aim of the announcement should be to increase visibility of the backports and ensure they are eventually reviewed. ...
That sounds like a lot of overhead to me. What actual problem are we solving with this? Best regards, Julian
