> On May 30, 2018, at 3:03 PM, Larry Hastings <la...@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.
_______________________________________________
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/
