Mozilla Project Weekly Status: March 9th, 2009


5.0.3 release this week
Anonymized Survey Results

  • The biggest request involves the review queue and the time it takes to get out of the sandbox. (24 requests)
  • There is a real need for better documentation (22 requests)
  • Tutorials are scattered across the internet and are often out of date. (21 requests)
  • The IDE’s/tools for writing and debugging extensions are lacking. (15 requests)
  • A few developers really want some sort of marketplace for extensions (6 requests)

Next step: some form of roundtable to reach out to developers to go over these results and what we are doing to address some of the big requests

Compatibility Update

  • 83.5% of add-ons compatible with 3.1
  • Will kick off 3.5 project plan this week so we can be ready for the version change.


Firefox 3.0.7

  • Release this Wednesday, March 4th

Firefox 3.0.8

  • Code freeze is a week from tomorrow
  • Aiming for mid-April release

Fx 3.1b3 (Shiretoko) – Status: Pending Release

Firefox Front End Work

  • 10 blockers left, only 1 of which is complicated
  • Good progress on code sprints for items that could opportunistically be taken for Firefox 3.1, but will be taken on trunk.

Beta 3 Progress

  • tagged and built early last week (one respin required)
  • QA underway and on schedule
  • on target for a release of this Thursday afternoon

Fx 3.5b43 (Shiretoko) – Status: Pending String Freeze

  • proposed schedule (not final):

    • String freeze: Thursday, March 19th at 11:59pm PDT
    • Code freeze: Monday, April 6th at noon PDT
    • QA start: Tuesday, April 7th at 9am PDT
    • Release: Tuesday, April 14th, afternoon PDT
  • will discuss this at tomorrow’s platform meeting and Wednesday’s delivery meeting before finalizing
  • you may also comment on the newsgroup thread

Reversioning to 3.5


Gecko 1.9.1

  • Now cranking on Beta 4. Groups other than JS are fixing issues as they find them at this point. JS still has a decent size bug list of 42.
  • Other areas are looking pretty good to wrap up blockers soon:
    • 14 final blocker bugs left in content.
    • 3 GFX final blockers.
    • 6 Layout final blockers.
    • 2 SVG final blockers.
    • JS with 42 blockers.
  • Triage needed. 47 noms are in the queue right now.
  • For weekly engineering meeting notes and other info see the Platform page.
  • 86 total 1.9.1 blockers (last week: 90).



  • Beta this Wednesday
  • Release in a week

TBird 3.0b3 (Shredder) – Status: In Progress

4 Comments on Mozilla Project Weekly Status: March 9th, 2009

  1. Quick tip for you FF Guru.

    Mozilla has just seeded their FTP site with the beta 3 folder and structure.

    Drilling down into the folders seems to indicate that some other OS builds have had their sub folders filled with content, as well as the Updates folder for partial updating via the .MAR files.

    However as I post this, the full beta 3 package folder for en-US is empty still.

    I didn’t see this folder present last night when I went to bed so it looks like they are getting the pump primed for an imminent release.


    Claus V.

  2. I go away for a few days, and everything busts loose. 🙂 Cool!

    I’ve been using shiretoko since b1. Even as a user who doesn’t know much about programming, I’d say it fully deserves its “3.5” designation. If it was commercial software, it’d be “4” at the very least.

  3. Still empty, but the Project Meeting notes did say Thursday afternoon. Just checked the Mozilla Releases page and they are showing release for today. Being as I am same time California now (until Nov 1) they will likely release while I am at work. I’ll check when I get home tomorrow morning and see what new.

  4. Curiously, I found what appears to be an official 3.1 beta 3 package (exe full install) for the en-US version here just a bit early:

    Firefox 3.1 Beta 3 –

    FileHippo has been a trusted source of key file-package downloads so I have little reason based on past-performance to doubt it is legit.

    After checking it out, I applied it to a test “portable” package I use for Firefox. Applied and run without issue.

    the “About” id’s the version as 3.1b3 and build ID below.

    Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.0.1 (.NET CLR 3.5.30729) ID:20090305152042

    So far it is stable and hasn’t tanked any of my current extensions (either already 3.1b2 compatible natively or forced into 3.1b2 compatible and worked fine). I did have to do a “nightly tester tools” force into compatibility for some of them after the over-install “upgrade” I did. But all seems good.

    Waiting for the “official” release as well for the rest of my systems’ FF update to 3.1b3. Then will compare Build ID’s just to make sure this version is the “real-deal.”

    So far, so good on this tester package, however.


    Claus V.

Comments are closed.