« previous week | index | next week »

Notices / Schedule

Firefox 4 Beta 7

• GC Compartments is on TraceMonkey, coming soon to mozilla-central and b7 relbranch, will require bake time
• new progress indicator landed yesterday (see bug 602964)
• update issues for Windows users were resolved today (see bug 602275)

Firefox 3.6.11

• Rebuilding now for a regression bug 601440 caused by a fix for a TB topcrash
• Date will be slipping to next Tuesday, a week from today

Firefox 3.5.14

• No rebuild needed, will ship next Tuesday with 3.6.11

Blocker Report

A handy list of Firefox 4 triage queries is available:

• Beta 7: 17 blockers
• Beta: 510 blockers
• Final: 391 blockers
  • TOTAL: 901 blockers
  • nominations: 160 nominations
  • ready to land: 11 blockers ready

Firefox Development

(from our goals):

Firefox

• [AT RISK] Finish Firefox 4
  • 160 Firefox/Toolkit blockers

• [ON TRACK] API-Complete Jetpack
  • Joint with Jetpack team
  • Currently working towards feature-complete beta SDK

• [ON TRACK] Stand up basic Firefox with Electrolysis
  • Joint with Platform
  • UI may not be functional, should launch and open a web page.
  • Project tracking page

Developer Tools

• [NEW] Finish Firefox 4 developer tools
  • 15 blocking developer tools bugs

• [NEW] Ensure that Firefox 4 ships with a compatible version of Firebug

• [NEW] Publish a roadmap for integrated developer tools in Firefox, including console, inspection, and js debugging

• [NEW] Develop long term plan for Skywriter maintenance/support

Platform

• As we wrap up the feature freeze with beta 7, we're creating a dashboard queries to coordinate our efforts for the remainder of the release. At a high level:
  • Review queues are getting clogged, lots of people with 12+ review requests with JST the winner at 44, roc at 21, ted at 22, peterv at 16, etc. Please go through your review queues and knock out all the blocker reviews ASAP.
  • Next we have a ton of blockers without owners. I'll be sending around queries so it's easy for people to find them, but component leads shouldn't wait.
  • Next after freeze, we have a spectacular list of crashes that we should grind through. Sheila Mooney is helping to pull together the next attack on crashes. See details here.

• Goals: Real list found here. Quick overview:
  • [ON TRACK] Finish Firefox 4 blockers.
  • [ON TRACK] Support Firefox Team to stand up a browser on Electrolysis.

GFX

Layout

• OTS font sanitizer integrated! (Q4 goal...)
• Blockers blockers blockers
  • 1 beta8 blocker
  • 39 betaN blockers
  • 141 blockers total
  • 14 requests need triage

JS

• Still doing perf work, getting progressively lower risk
• ES5
  • Landings
    • Compartments work
    • Fixed some errors adding properties to non-extensible objects
  • Almost ready to land
    • Strict mode this nearly done, although one notable followup (but has a patch) will remain after it
  • Current work
    • Give some eval code its own variable environment (no tainting calling context when code contains top-level var declarations); partial patch written, more work to do yet (one of the biggest remaining bits of strict mode to implement)

Tree Management

• power outage in colo yesterday bug 603452
• IT downtime closing 650castro this weekend for network upgrades on Sunday
  • will close mobile test tree
  • will *not* block any desktop build/tests or mobile builds
    • per discussion with stuart, will close tree for this anyway.
• Moving build machines into Build-VPN, possibly tomorrow? bug 602741

Roundtable

• What happens if you need to change APIs or strings now? [beltzner]
• Thank you Clint for adding support for --loop to runtests.py! bug 603517 [jst]
• Please have your teams complete their security reviews