Platform/2010-01-12

« previous week | index | next week »

Notices / Schedule

Firefox 3.0.17 / Firefox 3.5.7

• shipping today
• adjusted schedule to go for early January release to update users with fix for bug 534090 which affects major updates
• also took a fix to the NTLM regression as well as for the #1 topcrash on branches

Firefox 3.0.18 / Firefox 3.5.8

• new proposed schedule at links above:
  • code freeze January 19th
  • release Feb 16th
• tree is open, please work on blockers during this quieter RC period
• schedule tracks to three weeks later than original 3.0.17/3.5.7 schedule
• will try to coincide with a 3.6.1

Firefox 3.6 Beta Testers

• approaching 800,000 ADUs, stayed stable during the holidays
• about 20 nominations came in through the holidays, a few new code blockers were found

Firefox 3.6 Release Candidate

• one JS blocker left, should be landing today
• would like to co-ordinate RC builds with the Fennec guys to see if we can make sure we're both using the same gecko content in our relbranches

Firefox Future Releases

• please see the discussion in the newsgroups about the plan for a release code named "Lorentz", to be delivered early in Q1 with a focus on delivering out of process plugin support for at least Flash on Windows. We'll also discuss this in today's roundtable.

Blocker Report

Firefox 3.6 RC Code Completion

• 0 nominations to be triaged
• 1 code blocker remaining

All Blockers (includes website, release management, etc)
See more Firefox 3.6 related blocker queries, or learn about the new status and blocker flags

• Release Blockers (flag: blocking1.9.2 or blocking-firefox3.6)
  • 10 OPEN (-1 w/w) (8 are non-code, 2 are Fennec-only)
  • 0 FIXED but not yet fixed on mozilla-1.9.2
  • 0 nominations
  • Handy charts: Blocker snapshots, Blocker and Noms trends
• Approvals
  • email beltzner if you have approval requests needing attention
  • 32 requests
  • 5 approved but not yet fixed on mozilla-1.9.2 (+1 w/w)
  • Charts: Nominations snapshots

Browser / Front End

• no blockers
• you're going to see some UI churn on trunk, get used to it
  • This will cause change. Things will not be the same as before.
  • IF YOU SEE A CHANGE YOU DON'T LIKE: Please sit with it for at least 48 hours before blogging/tweeting/irc pinging to tell us how terrible it is.
  • Change is hard, but important. We value input more than insults.

• this quarter our big targets are:
  • starting UI changes for Firefox 4
  • reducing I/O on the main thread (performance)
  • supporting out of process plugins work (UI and integration work)
  • continuing to drive startup time
  • integrating jetpack, weave and iterating on personas

JS

• ES5 changes landing
• Interpreter rearchitecture underway
• WebGL typed arrays landed

Roundtable

• XULRunner branch release plan: We release XR on 3 branches. How long do we keep releasing a branch?