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
    • Code froze last Wednesday, a few days late
    • Builds for both releases were available Friday afternoon
    • Scheduled release date is November 12
    • Heading to beta later today
  • Major Update
    • Planning a major update after release
    • Aiming for ~2 weeks after release
  • Thunderbird
    • Currently scheduled for November 19
    • Highly dependent on Firefox
    • Aiming for about a week after Firefox
  • Firefox and 3.0.5
    • Schedules are on the wiki
    • Code freeze is for November 17 at 11:59pm PST
    • Using new short development, long QA cycle


Weekly common issues

  • Norton 360 updated yesterday
  • Still have a lot of issues with locked places.sqlite that aren't Norton 360 related.
  • Issues with Yahoo login is still the most common cookies issue

Firefox 3.1

Beta 2

  • tree now frozen and only open to blocking bugs, as well as a few scheduled exceptions
  • will be finishing and polishing from now until thursday
  • localizers will have next weekend to finish up (strings will stop landing as of Thursday)
  • release schedule is available online


  • Discussion in about re-evaluating in-product help for Firefox 3.1
    • Evaulating: How big should it be? Can we better organize the content in product help? What content should be covered in in-product help?
    • Current issue: Do we consider any page in in-product help to be mandatory for localization?
    • Dependent on Firefox code: Are there any other good places for help-topic links? Is it too late to even think about that?


this week 
40 (ar be bg bn-IN ca cs de el en-GB es-AR es-ES et eu fi fr fy-NL ga-IE gl he hi-IN is it ka kn lt lv nb-NO nn-NO pl pt-PT ro ru si sk sl sq sv-SE tr uk zh-CN)
last week 
3 (da ko zh-TW)
week before last 
3 (nl oc te)
10 (eo gu-IN hu id ja ja-JP-mac mk pa-IN pt-BR sr)
admins only
7 (af cy ku ml mn mr th)


  • Our top critical tracking issues blocking Beta 2 test development:
    • (bc) bug 458857 - TM: "Assertion failure: ngslots == tm->globalTypeMap->length()" with gc and generator as getters
      • blocking flag, needs a patch
    • (bc) bug 451843 - Running Dijit Tree Test with Content JIT enabled causes the TreeView not to appear.
      • TM is b2, but no one assigned to it yet. Might need to be punted to next milestone
    • (bc) bug 457660 - js1_8/genexps/regress-380237-01.js: InternalError: too much recursion (64bit)
      • TM is b2, but no one assigned to it yet. Might need to be punted to next milestone
  • Fx3.1 Feature testing progress spreadsheet
    • Testplan completion %: 84% (last week: 80%)
    • Estimated testcases: 752 (last week: 743)
    • Testcase completion %: 56% (last week: 46%)
      • Targeted % by Beta 2 ship: Testplans 100% | Testcases 50%
      • Targeted % by RC1 ship: Testplans 100% | Testcases 90%
  • As always, Feature Testplans and progress here.
  • Tracking Topcrashes from beta 1 (ss)
  • Created session on the 3.1 testplan wiki for QA/Support common issues
  • Private browsing testday pushed out again. Need time for internal testing / writing testcases this week (marcia)

Release Engineering

  • FF2.0.0.18 bug 461264 and FF3.0.4 bug 461267 going to beta today
  • TB2.0.0.18 waiting for last minute fix.
  • FF3.1beta2 bug 463036 waiting for go. Still doing last of the rel-automation work.


  • Docs coming up - working through worker threads + access control stuff on the messaging page
  • Add-ons compat page from justin (fligtar) is up and running.
  • Add-ons blog is up. Justin and others have been blogging.
  • Paul is starting to collect information on a specific page for add-ons developers