<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2015-08-14 12:26 PM, Sebastian
Zartner wrote:<br>
</div>
<blockquote
cite="mid:CAERejNafgNHEC=oH0MMeqNHGbG0zxvnA-iCQDQac4x03XbKDRA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On 14 August 2015 at 17:35, Mike Hoye
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:mhoye@mozilla.com" target="_blank">mhoye@mozilla.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
What else do you need to make a go/no-go decision to fix a
bug?<br>
</blockquote>
<div><br>
</div>
<div>What about enhancement requests? What is the criteria
to prioritize them?<br>
</div>
</div>
</div>
</div>
</blockquote>
I think it would be a mistake to conflate "knowing what I can work
on right now" with "knowing what our organization should build
next". While I have strong feelings about that "what should we build
next" question - and wow do I ever - I'm 100% sure that shackling
both of those questions to the same engine would be a horrible
mistake. <br>
<br>
For the sake of keeping focus, in this conversation I only care
about the (much, much simpler) question of how we can really know
what state a bug is in, and how we can leverage that clarity. <br>
<br>
<br>
- mhoye<br>
</body>
</html>