Platform/2009-03-31

« previous week | index | next week »

Notices / Schedule

Firefox 3.0.9

• Aiming for April 21 release

Firefox 3.0.10

• Scheduling a release for mid-late May
• Went through nomination list yesterday
• Blocker owners will be emailed today

Firefox 3.5 Beta 4

• string freeze: Thursday, March 19th at 23:59 PDT
  • 140+ strings landed between b3 and b4
• code freeze: Monday, April 6th
  • not looking feasible with current number of blockers
• QA start: Wednesday, April 8th
• release: week of April 13th

Blocker Report

• 34 blocker nominations (+13 w/w)
• 97 blockers left without a fix (+7 w/w)
  • 219 left to be resolved

Since 1.9.1 branch ...

Past 2 weeks ...

[ Platform Blocker Queries | Front End Blocker Queries ]

Summary

The Breakdown

• 5 blockers marked fixed1.9.1 over last week (-14 w/w)
• 22 bugs nominated for blocking over last week (-12 w/w)
  • blocking-firefox3.5+: 2 new unresolved (-2 w/w), 1 new resolved blocking-firefox3.5+ added (+0 w/w)
  • blocking1.9.1+: 23 new unresolved (-10 w/w), 24 new resolved blocking1.9.1+ added (+1 w/w)
• 98 patches approved for 1.9.1 over last week (+34 w/w)
• 124 blockers are FIXED but not yet landed on 1.9.1 (+28 w/w)

Browser / Front End

• Blockers: 9 remaining (-1 w/w) & 0 nominations
  • 3 need patches (eta 3 days of development time)
  • 6 need landing (bug 475066 needs testing on w32 and linux

• Polish update: Firefox is 51% shiny (+2% over last week)
  • Thanks go to: rstrong, jim (polish hard), and Dao (4)
  • 46 remaining easy polish bugs (whiteboard [polish-easy])
  • 36 remaining hard polish bugs(whiteboard [polish-hard])

GFX 1.9.1 Update

• Bug status:
  • 4 blocking 1.9.1+
    • Mostly crash bugs
    • Bug 470487 is a crash on plugin destruction, needs repro
    • 1 bug on triage list, waiting on response from Mats

Layout 1.9.1 Update

• Layout
  • x blockers (can we get a link to the query?)
  • x untriaged noms (can we get a link to the query?)
  • * SVG
  • x blockers (can we get a link to the query?)
• Video/Audio
  • x blockers (can we get a link to the query?)

Content Update

• 1.9.1:
  • 12 blockers
  • 1 untriaged nominations
• 1.9.next:

JS 1.9.1

• 31 blockers
  • 16 P1s including upvar bug 452498. Tryserver builds of upvar passed linux/mac perf, mochi, reftest, crashtest. Failed TUnit, browser-chrome, with what looks like a single bug.
  • 15 P2s
• 1 untriaged nomination

General 1.9.1

These are bugs that fall outside of components covered by the Gfx, Content, Layout and JS groups:

• 16 blockers
• 2 untriaged nominations

Security

Security Reviews

Still outstanding / to be scheduled

• native JSON
• DNS prefetching

Booked but not yet completed

• localStorage (today)

Tree Management

• Crash stacks for tests:
  • Needs to happen on try server still bug 483111
• Run unit tests on packaged builds bug 421611, bug 383136
  • Build config bits are done
• Greener-Tinderbox: work ongoing, machines still running. Updating to new changeset this week. Will have more results this week - many less reftest failures now that the color depth is set properly on the win32 boxes.

Roundtable

• Consider localStorage feature land on 1.9.1, bug 422526
  • on trunk since March 19th
  • security review coming today
  • see dev.planning thread on the topic
• Nick Nethercote will be doing a Valgrind brown bag presentation today
• Platform planning is ongoing. If there are items that you'd like to work on and want to communicate, please make sure to coordinate with the module owners and leads. Also, watch for dev.planning threads (such as this one ) as dev.planning is where features/work items will be discussed.
• XULRunner nightlies for 1.9.1 and/or mozilla-central? bug 445191
  • Needed for binary extension development
  • Can we get an eta?
• Planning worksheets thoughts (bsmedberg):
  • Some big-ticket items: XBL2, compositor, OOP plugins
  • But not process-per-tab...
  • How far out is 1.9.2? The planning worksheets make it hard to know when any particular item might be done.
  • Other than frameGC/refcounting and XBL2, is there other large/architectural work that should be focused on? Additional wrapper/xpconnect sanity?
• Tryserver overload every afternoon: is there a plan to get more slaves (especially Windows) and/or combine the slave pool with the main tree?