On 14/03/17 13:46, Michael Dürig wrote:
The only added overhead here is the extra email asking for review.
In my view the important part is that a review happens. I wouldn't require an email on the dev list, I'd be fine with a mention in an issue as well. The dev list is most likely a good place when a backport is more complex. E.g. changes of interfaces that affect other modules, index changes, anything that's not just a simple bug fix, etc.
standard CTR policy.
I would like to require an RTC policy for merges. Nothing fancy, but at least one more person who looked at the changes and was able to provide feedback either in an issue or on the dev list.
Regards Marcel
