Home Original page

[python-committers] Marking issues as "Release Blocker" priority (was Re: FINAL WEEK FOR 3.7.0 CHANGES!)

Donald Stufft donald at stufft.io
Wed May 30 15:09:22 EDT 2018 
> On May 30, 2018, at 3:03 PM, Larry Hastings <larry at hastings.org> wrote:
> 
> Yes, ISTM that the Dev Guide covers this.  The section on priority says:
> Triagers may recommend this priority and should add the release manager to the nosy list.
> In other words: if a dev thinks an issue should be a release blocker for version X, they should add the RM to the nosy list and make a comment recommending the issue be escalated to release blocker.  I thought it was telling that it doesn't instruct triagers to mark the issue as a release blocker themselves.


That seems a rather poor way of handling it TBH. A key thing is that an escalation for a decision should itself be a release blocker, because if someone thinks the issue might be, then we should get a decision on whether it is or not before the release goes out. Relying on a comment seems far too easy for the release manager to accidentally miss it or forget about it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20180530/5551a96d/attachment.html>
More information about the python-committers mailing list