Mozilla Project Weekly Status: 2009-03-30

ADDONS.MOZILLA.ORG (AMO)

3.1b3 compatibility up to 65% of total usage (+5%)
Total 3.1.* compatibility up to 84%, working to close gap on b3 compatibility
- Starting with beta 4, 3.5.* version will be available on AMO.
Continuing to work on improving AMO editor throughput, currently around 700 reviews/month, goal is to double this by end of Q2 and reduce review time.
Meeting with MoMo this week to talk about improving AMO story for Thunderbird with better editor support and more frequent updates of recommended lists for TB.

FIREFOX

Firefox 3.0.8
- On Wednesday, a critical vulnerability was posted to a public vulnerability list
- Release Drivers determined this was something we needed to fix, sooner than April 14 (the targeted release day of 3.0.8)
- Firefox 3.0.8 because a firedrill release, taking only two fixes (for the XSLT vuln and the CanSecWest vuln)
- We shipped on Friday afternoon, around 3:45pm officially
Firefox 3.0.9
- The release formerly known as Firefox 3.0.8 has now been rebranded Firefox 3.0.9
- Any fixes you were counting on to be released in Firefox 3.0.8 are now in Firefox 3.0.9
- A revised schedule was posted to the wiki link above, comments appreciated
- Aiming for April 21 release (a week later than scheduled)
Firefox 3.0.10
- Proposed schedule on wiki
- Targeting mid-May release
Final major update for Firefox 2.0.0.x
- Looking at issuing a final major update for Firefox 2.0.0.20
- Planning for shortly after 3.0.9
- More details this week
Firefox 3.5
- Firefox Front End Work
  - 11 blockers left, only 1 of which is complicated, 7 are just waiting to land
  - some likely UI opportunistic updates for Beta 4
    - updated privacy preferences pane bug 462041 (needs review)
    - updated clear recent history dialog bug 480169 (needs patch)
    - refactoring Places DB for performance bug 476297 (landed)
    - restoring only visible tabs first upon session restore bug 480148 (needs landing)
    - updates/fixes to PFS so plugin installers can be executed bug 435788 (fixed)
    - new tab experience – under evaluation, but requires string changes
- Beta 3
  - really solid, starting to gather feedback (seems positive)
  - already > 500,000 users
- Firefox 3.5 Beta 4
  - this will be the first release with the new version number
  - current schedule:
    - string freeze was Thursday at 11:59pm PDT
    - code freeze Monday April 6th – to be discussed at tomorrow’s meeting
    - release week of April 13th

GECKO

Gecko 1.9.1
- Beta 4 progress: Up a few bugs for JS at 37, up overall at 88 from 76.
- At the fix rates we’re seeing now, we’re going try to make a decision in tomorrow’s development meeting on the code freeze deadline of April 6.
- We’re in the middle of planning new features and work items for future releases. Everyone is encouraged to participate.
  - Each team has created a list and prioritized possible major work items for the next release.
  - There’s several ongoing dev.planning discussions of the work lists for each of the groups. Links to threads: Javascript, GFX, Layout, and Content.
  - For overall Platform planning, see this wiki page.
  - Next steps are to discuss the overall plan for what the next Gecko release will look like, not just features, but duration and timing.
- Blocker Status:
  - 9 final blocker bugs left in content. (14 last time)
  - 4 GFX final blockers. (Last week: 1)
  - 11 Layout final blockers. Six have patches. (Last week: 11)
  - 3 SVG final blockers.
  - JS with 37 blockers. Looks like about 16 of those bugs require a beta vector; however, only four of the 16 have patches. (Last week: 33)
- Triage needed. 27 noms are in the queue right now.
- For weekly engineering meeting notes and other info see the Platform page.
- 88 total 1.9.1 blockers (last week: 86).