info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Update on triage tags
24 views
Skip to first unread message
Dave Mandelin
May 22, 2012, 6:26:12 PM5/22/12
to
We've been using the new triage tags for a few weeks now. So far, we've mostly just been tagging things and getting experience with the new system.
Already, a few new needs have popped up. I put a description of the tags at https://wiki.mozilla.org/Platform/JS#JS_Bug_Triage_Tags so we can update them as they change. The most important new tags are:
- [js:t] means 'triaged'. We'll tag bugs that don't need any other tag this way in order to take them off the 'triage me' worklist.
- [js:inv:pX] is the new format for bugs needing investigation. If the bug needs investigation, it doesn't need a normal priority and it certainly doesn't need a target cycle. But it does need an investigation priority. E.g., a rare topcrash might be [js:inv:p3], because it's a real defect, but one of unknown and probably low significance.
Around the time the Fx16 cycle starts, I want to look at the outstanding Fx16 bugs, pick out a set that's not too big and worth fixing in the 16 cycle, and then defer everything else to Fx17 and beyond.
A few problems we don't have a good solution for yet:
- Querying to see which 'waitingforinfo' bugs have had info provided. This could probably be done with some sort of Bugzilla comment query, but we don't have one yet.
- Intermittent oranges and topcrashes are tricky. Most of them are too rare to merit effort, so it would be great if we had a separate dashboard for showing which ones are common enough to care about at the moment. We don't have that yet either.
Dave
Already, a few new needs have popped up. I put a description of the tags at https://wiki.mozilla.org/Platform/JS#JS_Bug_Triage_Tags so we can update them as they change. The most important new tags are:
- [js:t] means 'triaged'. We'll tag bugs that don't need any other tag this way in order to take them off the 'triage me' worklist.
- [js:inv:pX] is the new format for bugs needing investigation. If the bug needs investigation, it doesn't need a normal priority and it certainly doesn't need a target cycle. But it does need an investigation priority. E.g., a rare topcrash might be [js:inv:p3], because it's a real defect, but one of unknown and probably low significance.
Around the time the Fx16 cycle starts, I want to look at the outstanding Fx16 bugs, pick out a set that's not too big and worth fixing in the 16 cycle, and then defer everything else to Fx17 and beyond.
A few problems we don't have a good solution for yet:
- Querying to see which 'waitingforinfo' bugs have had info provided. This could probably be done with some sort of Bugzilla comment query, but we don't have one yet.
- Intermittent oranges and topcrashes are tricky. Most of them are too rare to merit effort, so it would be great if we had a separate dashboard for showing which ones are common enough to care about at the moment. We don't have that yet either.
Dave
Nicholas Nethercote
May 22, 2012, 7:41:47 PM5/22/12
to Dave Mandelin, dev-tech-js-en...@lists.mozilla.org
On Tue, May 22, 2012 at 3:26 PM, Dave Mandelin <dman...@mozilla.com> wrote:
>
> - [js:t] means 'triaged'. We'll tag bugs that don't need any other tag this way in order to take them off the 'triage me' worklist.
I guess this means that we should just pre-emptively add this to all
>
> - [js:t] means 'triaged'. We'll tag bugs that don't need any other tag this way in order to take them off the 'triage me' worklist.
bugs we file ourselves for bugs that are just minor clean-ups and that
kind of thing? (e.g.
https://bugzilla.mozilla.org/show_bug.cgi?id=757336).
Nick
Dave Mandelin
May 22, 2012, 7:47:21 PM5/22/12
to Dave Mandelin, dev-tech-js-en...@lists.mozilla.org
Dave
Dave Mandelin
May 22, 2012, 7:47:21 PM5/22/12
to mozilla.dev.tech.j...@googlegroups.com, Dave Mandelin, dev-tech-js-en...@lists.mozilla.org
On Tuesday, May 22, 2012 4:41:47 PM UTC-7, Nicholas Nethercote wrote:
0 new messages