Firefox 3/Gecko 1.9 Meeting Details
- Tuesdays – Firefox 3 – 11:00am Pacific, 2:00pm Eastern, 18:00 UTC
- Mozilla Building S – Central Area
- 650-903-0800 or 650-215-1282 x91 Conf# 217 (US/INTL)
- 1-800-707-2533 (pin 369) Conf# 217 (US)
- irc.mozilla.org #granparadiso for backchannel
Firefox 3: issues for final ship
- l10n of new mozilla.com underway – requirements are webbugs, total open bugs are in () in the Web bugs column
- General QA (tchung)
- RC2 targeting 6/4. Planned testing is completed, and we’ll be using the extra day to cover feedback, webpages, bug verifications, and focus areas. See testplan for latest updates.
- Notable bugs found here.
- bug 434624 – safebrowsing file not updated on first launch. This was RC2-’d, but a fix and test has been verified on tryserver.
- We had another high activity RC2 test day on Fri, May 30th. Over 35 people joined us. Coce was again the top community tester! There was a lot more activity and interaction than that the results show.
- Leak Testing Update (tomcat)
- Topcrashes update (ss)
- Summary (as of 2008-06-02): In RC2, we fixed four topcrashes in cluding the number one. Of the top 20, we’ve can see that at least 7 (more likely 8) are caused by add-ons or plug-ins. We’ve been in contact with several plug-in and extension vendors to get those bugs fixed including Silverlight, Piclens, and Google. This is excellent progress for an RC and we hope to continue to make progress in 3.0.1 based on feedback from RC2.
- See wiki for latest crash report
- bits signed, ready to go. Waiting for formal “ok to start pushing to mirrors”.
- There are about 40 bugs marked blocking22.214.171.124+/blocking126.96.36.199?, though some nominated for RC2 aren’t on that list.
- There are 400+ bugs marked wanted1.9.0.x+/wanted1.9.0.x?
- how should we be flagging bugs?
- blocking1.9.1+ actually means blocking.
- If a bug is not a blocker, but still of high importance to the release, it will be marked wanted1.9.1+.
- The priority field should be used on each wanted1.9.1+ field in order to identify which bugs to work on first.
- P1 is high complexity, long-running tasks.
- P2 are of moderate complexity
- P3 are low priority bugs that will likely fall off the list.
- what work is underway?
- what work needs attention / is at risk?
- mozilla-central is now open for business, sheriff-approved checkins should go there before being back-ported to CVS which is now the 3.0 Branch repository