<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 10:21 AM, Donald Stufft
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:955F645F-C2B9-4811-BB0E-E8D5CDA85D7E@stufft.io">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On May 30, 2018, at 1:15 PM, Larry Hastings <<a
href="mailto:larry@hastings.org" class=""
moz-do-not-send="true">larry@hastings.org</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class=""><span style="caret-color: rgb(0, 0, 0);
font-family: Helvetica; font-size: 12px; font-style:
normal; font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration:
none; float: none; display: inline !important;" class="">ISTM
that opinions vary on what constitutes a "release
blocker", and maybe empowering only the release managers
to make that call would be a good way forward--which is
what ISTM is what the Dev Guide already says anyway. But
I guess not!</span></div>
</blockquote>
</div>
<br class="">
<div class="">I think that RMs are empowered to decide what is a
“real" release blocker, but you need some mechanism to flag an
issue as potentially a release blocker for the RM to make a
decision on it. Making a decision on that potentially release
blocker should also itself be a release blocker (because if it’s
possibly a release blocker, then we should treat it as such
until the person empowered to make that call has decided one way
or another).</div>
<div class=""><br class="">
</div>
<div class="">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>
</blockquote>
<br>
Yes, ISTM that the Dev Guide covers this. The section on priority
says:<br>
<blockquote>Triagers may recommend this priority and should add the
release manager to the nosy list.</blockquote>
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 <i>doesn't</i> instruct triagers to
mark the issue as a release blocker themselves.<br>
<br>
<br>
<i>/arry</i><br>
</body>
</html>