From MozillaWiki
Jump to: navigation, search

« previous week | index | next week »

Firefox Product Delivery Meeting Details

  • Wednesdays - Firefox 3 - 11:00am Pacific, 2:00pm Eastern, 18:00 UTC
  • Mozilla Building S
  • 650-903-0800 or 650-215-1282 x92 Conf# 8605 (US/INTL) <-- note new extension: x92 instead of x91!
  • 1-800-707-2533 (pin 369) Conf# 8605 (US)
  • #shiretoko for backchannel

NOTE: See Platform#Meeting_Notes for development meeting notes

Firefox 2.0.0.x / 3.0.x

  • Firefox and 3.0.4
    • Shipped (yay)
    • Aiming for major update beta by end of week
    • Aiming for major update final in early December
  • Thunderbird
    • Shipping today
  • Firefox and 3.0.5
    • Code freeze was two days ago
    • Slush is yummy
    • Still taking patches for five blockers (and only those five)
    • Aiming for release in mid December after long QA period


Weekly common issues

  • Locked/corrupted places.sqlite is still common
  • New 3.0.4 issues (tracking on RRRT page):
      • more crashes (may be related to memory usage, or that could be a red herring?)
        • OSX: bug 459531
        • Windows: crash on 0x00 may be AVG8 bug 446224, Backdoor.Ulrbot.C rose a lot of places in the topcrashes list after 3.0.4 came out bug 434403.
      • Firewall blocks connectivity (Norton mostly)
      • Firefox 3.0.4 uses 100% of the CPU while idle bug 464864
      • Unsolved memory leak in windows: bug 457234?

Firefox 3.1


(see development meeting notes)

Beta 2

Branching Post Beta 2

  • plan is to create a new repository for the branch (see the dev.planning thread for details)
  • releng work being tracked in bug 464640
  • documentation needs to be written for ..:
    • how to pull branch
    • how to apply to branch, how to uplift from central to branch

Next Milestone

  • beltzner has been talking with a bunch of people, trying to break things down and understand how to make this decision
    • goals: get more beta users, ensure quality of release, meet new "smaller, more frequent" release cycle
    • considerations: add-on compatibility drives usage, JS engine replacement means we need broad web compatibility testing, several features landed late in the b2 cycle, b2 now estimated for first week of december
    • requirements:
      • declare platform frozen for add-on development and themers
      • quickly identify any l10n changes required to get that work scheduled
      • do not accept any new features, only interaction and functional updates based on feedback (bugs, discussions, suggestions)
      • leave enough time to find compatibility issues & react
      • ensure we get user base testing the breadth of the web
    • discussion to date:
      • lots of blockers implies too much change to only have one more milestone
      • history shows that at this point we usually need another beta
      • hard to tell
    • proposal:
      • plan next milestone as RC1
      • evaluate early in december based on blocker take rate and early feedback
      • get clarity about impact on shipping schedule


Support Firefox Day is Friday!



  • Awaiting Beta 2 builds
  • Need to readjust testplan/resources to new dates
  • Results from trunk testday last week
    • 3 new community members, 83 tests ran

Release Engineering


  • Add-ons plan in place
    • Mail to go out to all add-ons developers asking them to sign up for about:addons
    • about:addons likely to be done at the end of next week
    • Beta2 messaging - update now, we'll stop breaking stuff
    • Dashboard is in place, starting to see slow updates
    • Starting to get technical feedback via Paul, Mark and Sheppy
  • Beta2 messaging outlined but not written yet
    • Arun working on access control docs
    • Sheppy making progress on worker threads docs
    • Starting to get partners in place for final for other items


  • Getting word out about new l10n - DB to synch with SethB
  • Updated list of pages to be updated by final release:


  • antiphishing in Firefox 2
  • major update(s) for Firefox 2 -> 3
  • add-on compatibility outreach
  • Polish update: Firefox is 8% polished
    • 7 of 57 easy polish bugs complete
    • 0 of 23 hard polish bugs complete
    • Thanks to Marco, Dao, Gavin, Vlado Valastiak and Shawn