<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 05/24/2018 10:08 AM, Ned Deily
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:E036A817-BE1E-48F7-AB0E-8AA2DD486206@python.org">
<pre wrap="">If you (or anyone else) feels strongly enough about it, you should re-open the issue now and make it as a "release blocker" and we should discuss the implications and possible plans of action in the issue.</pre>
</blockquote>
<br>
About that. According to the Python Dev Guide:<br>
<blockquote>Whether a bug is a *release blocker* for the current
release schedule is decided by the release manager. Triagers may
recommend this priority and should add the release manager to the
nosy list.<br>
<br>
<a class="moz-txt-link-freetext" href="https://devguide.python.org/triaging/#priority">https://devguide.python.org/triaging/#priority</a><br>
</blockquote>
Of course, a particular release manager (e.g. Ned here) can change
the policy for their releases. But by default, unless you're the
release manager for release X, you should not mark issues as
"Release Blocker" for release X. This seems like a sensible policy
to me, and effective immediately I'm going to hold to this policy
for my releases (3.4 and 3.5).<br>
<br>
<br>
<i>/arry</i><br>
</body>
</html>