Firefox3/StatusMeetings/2007-11-13

From MozillaWiki
Jump to navigation Jump to search

« previous week | index | next week »

Firefox 3 Meeting

Meeting Details

  • Tuesdays - Firefox 3 - 11:00am Pacific, 2:00pm Eastern, 19:00 UTC
  • Mozilla Building S - <script> conference room
  • 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

PRD Status Update

Open Action Items

Schedule & Tree Rules

Work in progress

  • Places (Places team)
  • Download Manager
  • Password Manager (dolske)
  • Add-ons Manager (Rob Strong, Mossop, mwu)
  • Security, Privacy, Identity
  • Installer
  • User Experience
  • Theming/Visual Makeover

Security Review

  • Design Review Proposal
  • Suggested order for review
    • Password Manager (done)
    • Offline Apps ([done])
    • Web Content Handlers (done)
    • Microformats (mkaply)
    • RSS (sayrer)
    • Add-Ons (rob_strong) (in progress)
    • Places (dietrich) (in-progress review doc, need to schedule)
    • Cross-domain XMLHttpRequest - Done.
    • Distribution/Customization
    • ContentEditable
    • Private Browsing
    • Malware Protection

QA Status/Topics

  • Results from M9 testing
    • No shipstoppers
    • Smoketests: 100% completed
    • FFTs: 70% completed
    • Plugins/ Top Sites / Extension Testing: 80% completed
    • L10N spotchecks: 20% completed
    • M9 Bug verifications: 2 left to verify
    • Issues found are in the link above
  • Beta 1 Testday results
    • 1200+ litmus tests by Community
    • 500+ litmus tests by l10n Community
    • 58 failed testcases
    • 66 unclear/broken testcases
    • 50 new Community Members total, and 35 using Litmus
  • Beta 1 round 2 testday this friday. All devs, please join us on #testday again for Q&A.
  • Leak testing ongoing. See wiki for results and issues found. (tomcat)

Localization Topics

Round table

Gecko 1.9 Meeting

Meeting Details

  • Wednesdays - 11:00am Pacific, 2:00pm Eastern, 19:00 UTC
  • Mozilla Building S - <script> conference room
  • 650-903-0800 or 650-215-1282 x91 Conf# 217 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 217 (US)
  • join irc.mozilla.org #granparadiso for backchannel

General Discussion

  • Our top priority is fixing all P1 bugs.
  • If there's a P1 in your review queue, and you aren't working on fixing a P1, please review the P1 first.
  • If you aren't working on a P1 or P2, please check the Beta 2 blocker list to see if there is a bug you can kill or help/relieve someone else.
  • Currently aiming to be code complete for Beta 2 on Dec 7.
  • 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

Blockers report:

Platform Round Table

  • GFX Update
    • Status of prioritization of Beta 2 P1s and Beta 2 Blockers?
    • 1 P1
    • 6 P2s
    • 14 printing bugs.
  • Layout Update
    • Status of prioritization of Beta 2 P1s and Beta 2 Blockers?
  • Content Update
    • Status of prioritization of Beta 2 P1s and Beta 2 Blockers?
  • Mac OS X Update
    • 20 Blockers remaining.
    • 1/2 are planning to do for M10.
    • Status of prioritization of Beta 2 P1s and 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
Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox3/StatusMeetings/2007-11-13&oldid=74382"