From MozillaWiki
Jump to: navigation, search

« previous week | index | next week »

Firefox/Gecko Delivery Meeting Details

  • Wednesdays - 11:00am Pacific, 2:00pm Eastern, 18:00 UTC
  • Mozilla Square Conference Room
  • 650-903-0800 or 650-215-1282 x92 Conf# 8605 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 8605 (US)
  • #planning for backchannel
  • (the developer meeting takes place on Tuesdays)

Upcoming Product Releases

January 13 - 20 2010

Firefox 1.0 for Maemo RC3

  • Bug Fixes for blockers (4 left) are still underway
  • Versioning on nightly build repos are broken currently
  • RC3 is looking at being code freeze at the end of this week

  • AMO 5.5 launches today, highlights are revamped localizer dashboard and language filter for search results (more areas of site coming soon)

January 2010

Firefox 3.6

  • QA is working on full functional tests, going well
  • one potential RC respin candidate bug has been found, evaluating
  • still working on an exact ship date, two proposed dates are Jan 19 and Jan 26

Firefox 3.0.17 Major Update Offer

  • uptake on 3.0.17 is leveling off, majority of users have migrated
  • will start doing a prompted major update offer to 3.5.7 users tomorrow morning

February 2010

Firefox 3.0.18 / Firefox 3.5.8

  • proposed schedule at links above
  • long code freeze -> build period
  • might try to co-ordinate with Firefox 3.6.1

Lorentz project looking to release a beta in next 4 weeks or so (bsmedberg: two weeks, really, but depends on 3.6 schedule and other stuff)

  • Firefox 3.6 + out of process plugins
  • will likely be shipped as a minor update to Firefox 3.6 users
  • At some point, want to update current 3.6 beta channel users to the Lorentz beta... conflict with 3.6.x beta testing?



  • common issues
  • 3.5.7 issues: Unable to search (some say from search bar, some say from address bar, some say the whole nav bar isn't working/grey'ed out). [1][2][3][4]

Product Development

  • great progress on process separation stuff
  • a lot of exciting work happening on the platform layer
  • much discussion about how we'll ship various items to users
    • some things will be developed on trunk and then back-ported (like the Lorentz project) and shipped as minor updates
    • other things will require a major update
    • beltzner to blog more about this later

More details available in the platform meeting notes.


  • Lorentz l10n changes:
    • build systems will be up for both lorentz and 1.9.2 in parallel, including dashboards
    • added strings will be ignored on 1.9.2 with fallback strings on lorentz, so lorentz will report them missing, 1.9.2 will not report them obsolete
    • localizations and language packs made for 3.6 will continue to work thanks to the fallback strings
    • no string removals for lorentz, so l10n targeting lorentz will work on 1.9.2 pre-lorentz
  • Search repackaging changes with Lorentz? Multi-locale builds want the search engines to be in the jar, which we're doing for fennec, but not for Firefox desktop. Changing that without testers in the wild scares Pike, maybe Lorentz has the coverage we need?
  • Locale updates for firedrills and -like releases, are we actually more safe on regular releases? What would it take to feel good about taking them? Yes, Pike wants to take them, still.


  • Firefox 3.6 RC1 Testing FFT Results (Please review)
  • Fennec:
    • Recap of the Testday
    • Ongoing testing for RCs
  • Wince (Tegra) deprioritized

Release Engineering

  • When to unthrottle major update for 3.0.17->3.5.7? Today/tomorrow
  • Funnelcake 10 tonight/tomorrow, but can be rescheduled to next week if needed


  • Compatibility at 81%
    • CoolPreviews should happen this week
    • Continuing to ping Google Gears folks
    • Only a few stragglers, one big one is IE Tab (but not Coral IE Tab)
  • Reviews back in full swing, lots of applicants for AMO Editor team
  • AMO 5.5 launches today, highlights are revamped localizer dashboard and language filter for search results (more areas of site coming soon)

Web Dev

  • Vaguely named procedures page linking to a draft plugin updating procedure
  • Les wrote about what we're doing for plugins. Read more about the plugin directory or PFS2. Goals for plugins in Q1:
    • Get vendors updating their own plugin data as a part of their release process using our tool
    • Assign a point person responsible for managing this data (security makes sense, since they are watching updates and advisories)
    • Get cross-browser plugin checking working (yes, for IE too)
    • Pretty up plugin directory messaging and usability
  • Socorro 1.4 is triaged, so if you are interested in crash reporting and you have an urgent need and it's not in there, please let us know in the thread or email me