Changes

Jump to: navigation, search

Firefox3/StatusMeetings/2007-11-13

1,609 bytes removed, 18:39, 14 November 2007
Gecko 1.9 Meeting
* 26 of the 43 Blockers have a patch of some sort (not a reliable number).
* Tree Rules: blocking1.9+ and approval1.9+ are clear to land. Closer to beta 2 code complete date, we'll restrict to only P1s.
 
=== Beta 2 criteria, proposal 1 ===
 
* '''Should''' go in for beta 2:
** Bugs likely to cause regressions -- it is better to land risky patches for beta 2 than later!
** Bugs that prevent many users from browsing the web on a daily basis
** Security issues
** Top crashers
* '''Can''' go in for beta 2:
** Memory leaks
** Performance issues
** Major regressions from Firefox 2
** Functionality in support of a P1 PRD item (?)
 
=== Beta 2 criteria, proposal 2 ===
 
Maybe listing all those criteria (like in "proposal 1") isn't especially productive: it leaves out many reasons bugs might be "important" for other reasons. For example, a bug might be important now because it affects Leopard, or because we suddenly realized it is critical for Chinese users, or because web sites are using XHR more than they did when we released Firefox 2. ("Bugs that prevent many users from browsing the web on a daily basis" gives a way out, but why not make that the only criterion?)
 
* Should go in for '''beta 2''':
** The 10% most important blockers
** Anything risky (likely to cause regressions) among the next 10% most important blockers
* Should go in for '''beta 3''':
** The next 10% most important blockers
* Should be '''cut''' from Firefox 3:
** New features that have not gone in yet.
** Any patch with too much risk of regressions to go in at the beginning of the beta 2 cycle (because there will never be a safer time to land them)
** The rest of the "blockers" (80% ?)
 
"Importance" should be judged largely on how much the bug would "prevent users from browsing the web on a daily basis". This allows bugs to be compared on equal footing whether they are crashes, regressions, Leopard bugs, or even long-standing bugs that we had hoped to fix in Firefox 3. (One major exception to this is security issues.)
=== Blockers and Noms ===
=== Platform Round Table ===
* GFX Update
** Status of prioritization of Beta 2 P1s and [http://tinyurl.com/2yy5hv Beta 2 Blockers?** 1 P1** 6 P2s** 14 printing bugs.]
* Layout Update
** Status of prioritization of Beta 2 P1s and [http://tinyurl.com/2xbc9n Beta 2 Blockers?]
* Content Update
** Status of prioritization of Beta 2 P1s and [http://tinyurl.com/29wjn4 Beta 2 Blockers?]
* Mac OS X Update
** 20 Blockers remaining.Here is a summary of our P1 and P2 situation:*** 8 P1s and P2s** 1/2 * 4 of those bugs are planning the same or very similar focus issues, which Steven is working on. Steven is making great progress on all of them. It is a little too early to do for M10start duping them against each other, but that will probably happen.** Status * 3 of prioritization those bugs are mine, 2 of which I have made significant progress on already. The third bug I am very familiar with.*** 1 of Beta 2 P1s those bugs belongs to Mats Palmgren, he has posted a patch already and is in the review process.** Beta 2 Blockers?]
* Build Tools/Toolkit
** {{bug|346214}} - Vista icon doesn't build on current refplatform. Will require updating MozillaBuild + Platform SDK on Win32 refplatform
Confirm
1,067
edits

Navigation menu