<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 05/30/2018 11:59 AM, Brett Cannon
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAP1=2W5_ePtrtnTpwTe+NSNdME6N3SE1baenTzoZPNnzoP_4Fg@mail.gmail.com">
<div dir="ltr">On Wed, 30 May 2018 at 10:21 Donald Stufft <<a
href="mailto:donald@stufft.io" moz-do-not-send="true">donald@stufft.io</a>>
wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div
style="word-wrap:break-word;line-break:after-white-space">
<div><br>
</div>
<div>So I think for the system to work, you need to either
allow anyone to flag an issue as a release blocker, and
the RM is empowered to say “No this really isn’t” and
unflag it, or you need two flags, for release blocker,
and maybe release blocker, and both block the release.</div>
</div>
</blockquote>
<div><br>
</div>
<div>Yep, or as MAL suggested, a "potential release blocker"
or something where we expect only RMs to push something all
the way up to an actual "release blocker". <br>
</div>
</div>
</div>
</blockquote>
<br>
I suggest we simply use the existing "critical" priority to also
mean "potential release blocker". If not, what would be the salient
difference between a "critical" bug and a "potential release
blocker" bug?<br>
<br>
<br>
<i>/arry</i><br>
</body>
</html>