Fwd: REST APIs, and Tags

Benjamin Smedberg benjamin at smedbergs.us
Mon Feb 15 14:55:02 UTC 2010

On 2/15/10 9:43 AM, Gervase Markham wrote:
> On 11/02/10 19:01, Frédéric Buclin wrote:
>> IMO, an additional bug status doesn't fix anything. You move the problem
>> from UNCO/NEW to NEW/READY.
> Except that you can't file bugs as READY.
> And there is a distinction between "yes, this is definitely a problem"
> (->  NEW) and "this bug report is ready to be fixed" (->  READY).

This gets into b.m.o-specific workflow, but neither of those states 
represents what I'm really interested in as module owner. What I want to 
know is "have I or my peers looked at this bug, assigned it a 
priority/owner, and commented setting expectations"? There are many bugs 
which have good testcases and are "ready to be fixed" which I have not 
prioritized... in fact many of the bugs filed in the XPCOM component *come 
with patches*, and I still would like to triage them.


dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org

More information about the developers mailing list