Firefox 4 Re-Triage Results, For Everyone

11 views
Skip to first unread message

Damon Sicore

unread,
Dec 15, 2010, 11:20:32 PM12/15/10
to mozilla.dev.planning group
All,

In a coordinated effort, the Firefox and Platform engineering teams wrapped up the last of our blocker re-triage events, reducing the overall blocker count by an AMAZING 353 BUGS! This is an approximate decrease of 35-40% from our original blocker bug count. Blocker bugs are those which must be killed before we can ship the product. The bug count reduction above includes those that we've moved to the next release, decided just shouldn't block, and some that we've dropped entirely. Of course, this is a fuzzy metric as not all bugs are created equal, but this is a huge step forward as now we have a ton more clarity into the release.

Everyone really pulled together, and the results show we're all committed to relentlessly driving towards shipping a killer Firefox 4. I'm really impressed by the full turnout for each session, and most inspiring was seeing all the new faces fearlessly participating in what can be a very intimidating process. I'm proud that we've assembled such an amazing group of engineers and leaders, and everyone's performance the past three days is exemplary.

Now we must stay on target by only working on the most important issues required to ship Firefox 4 and keep a keen eye on those blocker and nomination lists to make sure we maintain this renewed focus.

Top job team!

All my best,

Damon


Mike Beltzner

unread,
Dec 15, 2010, 11:44:25 PM12/15/10
to Damon Sicore, mozilla.dev.planning group
----- Original Message -----
> wrapped up the last of our blocker re-triage events, reducing the
> overall blocker count by an AMAZING 353 BUGS! This is an approximate
> decrease of 35-40% from our original blocker bug count. Blocker bugs

For those who are curious to know which were dropped:

226 were "minused" (http://bit.ly/fx4-minused)
79 were "cleared" (http://bit.ly/fx4-cleared)
49 were re-targeted at a branch support release (http://bit.ly/fx4-branch)

(Of course, drivers and triagers can make mistakes. If you feel a bug was unblocked in error, renominate with full rationale as to why the issue should block the release. "Because I think it's important" is not a valid reason; if you think that something important was missed, add a [d?] to the whiteboard.)

This leaves us with a total of 559 blockers: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2:final,beta From that list:

185 are regressions (https://bugzilla.mozilla.org/buglist.cgi?quicksearch=OPEN%20blocking2:beta,final%20kw:regression)
21 are perf related (https://bugzilla.mozilla.org/buglist.cgi?quicksearch=OPEN%20blocking2:beta,final%20kw:perf)
41 are crashers (https://bugzilla.mozilla.org/buglist.cgi?quicksearch=OPEN%20blocking2:beta,final%20kw:crash)
338 are feature work (https://bugzilla.mozilla.org/buglist.cgi?quicksearch=OPEN%20blocking2:beta,final%20-kw:regression,perf,crash)

(note that some of those are doubly counted)

cheers,
mike the bugzilla inquisitor

Gary Kovacs

unread,
Dec 16, 2010, 12:59:37 AM12/16/10
to Damon Sicore, mozilla.dev.planning group
Great progress everyone!

Thank you for the effort.

-gary

Reply all
Reply to author
Forward
0 new messages