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)
  • 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 -> 3.0.5 Major Update
    • Shipped January 8 (six days ago)
    • Uptake isn't very good yet, but still monitoring
  • Firefox 3.0.6
    • Code frozen (minus one bug, which we may or may not take)
    • QA is currently testing
    • If all goes well, will start builds Monday, January 19
    • Aiming for final release date in early February
  • Firefox 3.0.7 (no wiki link yet!)
    • Targeting one month after 3.0.6
    • Look for a post to dev-planning about final schedule by Friday
    • Planning to re-open the tree shortly after builds start for 3.0.6

Firefox 3.1 Development

Development Update

  • large outstanding set of P1 blockers (lion's share in TraceMonkey/JS Engine)
  • moving code freeze for Beta 3 to Jan 25th to contain
  • goal will be to get to 0 P1s in all components ASAP and then cut into P2s until freeze; this should prevent significant delay to final release date for Firefox 3.1

(see development meeting notes for more details)

Daily users

  • ~ 250k users on the Firefox 3.1 Beta 2
  • ~ 11k users on Shiretoko nightlies
  • ~ 5k users on Minefield nightlies

Beta 3 New proposed schedule based on code slip:

  • String freeze will maintain in place
  • Code freeze is January 25th, 11:59pm PDT
  • QA Start is January 27th, 9:00am PDT
  • Release is targeted at Feb 2nd, noon PDT


  • Malware reports on the rise (redirected searches/pages, mostly, but also unblockable popups) 10 in a small sampling this week.
  • Do we have "official" things to say for users of unsupported OSes?


Firefox 3.1 Beta 3 status 
  • 53 locales opted in and green
  • 4 locales green, not opted in (gl (red on windows), id, ka, uk)
  • 10 locales building and red, -2 far fetched (as, ta), -2 on the hook (ml, sl), further poke to bg, cy, da, ko, mn, oc?
string freeze break requests 
gather a list of bugs for triage for breaks post Beta 3 by next week. Please CC and add [missed string freeze] to the whiteboard to make them show up on this query


  • Beta 3 Testplan posted
  • Firefox 3.1 Feature testing progress:
    • Testplans (92% completed)
    • Testcases (81% completed)
  • Need to verify 373 fixed1.9.1 bugs
    • Will be creating a QMO project to leverage community help
  • Organizing a testweek on Places Testing in QMO (tracy)
  • Major Update test run of 3.0 -> 3.1b3 (ETA mid-late jan)
  • Converting Fx3.1 smoketests to Mozmill automation this quarter

Release Engineering

  • Formal "handover to build" date? Sunday afternoon PST is better NZ time. Do code freeze earlier on Sat maybe?
    • builds needed by QA before 9am PST Tuesday 27th.
  • l10n improvements, all nightlies on all branches now good.
  • two unexpected downtimes since last week, all appears ok now, but let us know...


  • Add-Ons are now 54% compatible with Firefox 3.1 (exactly like a week ago).
  • Add-Ons review queue is beyond 600 nominated and updated Add-Ons. Details at Cesar Oliveira's post.
  • Two official AMO blog posts on the topic: from Nick and Rey


  • Yahoo! pushing fix for bug 471816 on 2-Feb-2009, and will work with us on QA beforehand.


  • On the chopping block to work with slater / bottoms on perf messaging.
  • Docs are in good shape
  • Add-ons manual would be nice to have, but unlikely to happen by the end of Feb


  • Working draft of Web site update plan posted [1]


  • dveditz to drive a project to see if we can have a "check your plugins" site where users can go to determine if their plugins are up to date, and if not, find links to updates (see bug 391433 for details)
    • beltzner, johnath, chofmann asked to be cc'd
  • justin agreed to follow up with morgamic to ensure that we could throttle Major Update snippets on a per version / channel basis (to allow users to "Check for Updates..." to Firefox 3.1 on launch day, but not have the offer given to users who do not explicitly check)
  • beltzner to follow up with joduinn, nthomas, axel about code handoff dates

Bugzilla Queries for bug verifications