The State of 2.20 Blockers

[Myk Melez]

With permission from Dave, I've unblockered a bunch of 2.20 blockers, 
following the criteria laid out by Dave in IRC: "If it's not a 
regression from 2.18 and it's not a critical problem with something 
that's already landed, let's push it off."

If you disagree with one of my decisions, re-request blocking2.20, and 
Dave will take another look at it.  Note that you can still land fixes 
into 2.20 which are not 2.20 blockers; we'll still take other low-risk, 
high-reward polish fixes, even though they won't block the release.

Note also that we've switched to a time-based release cycle.  That means 
we're going to ship 2.20 when it's time to do so (i.e. now, or as soon 
as possible thereafter), not when it has all the fixes and new features 
we want for it.  We know this means shipping with bugs we don't want.  
We hope and intend for the benefits of regular releases to outweigh that 
downside.

There are now 15 2.20 blockers 
<https://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking2.20%2B>.  
Also, I've labeled the low-risk, high-reward polish fixes 
<https://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&status_whiteboard_type=substring&status_whiteboard=%5Bwanted+for+2.20%5D&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED>I'd 
like to see make it into 2.20 with the "[wanted for 2.20]" status 
whiteboard tag.  Please prioritize these bugs in your development and 
review time so we can quickly ship a great 2.20.

-myk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20050421/d751a08a/attachment.html>