Platform/2009-12-15: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 58: Line 58:
** frameLoader.attachChildGlobal(node, "propertyName") to create a property on |node| corresponding to the child's global object, thereby exposing the wrapper.
** frameLoader.attachChildGlobal(node, "propertyName") to create a property on |node| corresponding to the child's global object, thereby exposing the wrapper.
** Grass-roots support (mrkbap, peterv) for a change in terminology: Cross-Process Object Wrappers (CPOWs)?
** Grass-roots support (mrkbap, peterv) for a change in terminology: Cross-Process Object Wrappers (CPOWs)?
** Look for my patch in {{bug|516522}} at the first light of the fifth day (i.e. the end of this week).
** Look for my patch in {{bug|516522}} at the first light on the fifth day (end of this week).


= Platform-specific Support Update =
= Platform-specific Support Update =

Revision as of 18:31, 15 December 2009

« previous week | index | next week »

Notices / Schedule

Firefox 3.0.16 / Firefox 3.5.6

  • everything's signed off, releasing today

Firefox 3.0.17 / Firefox 3.5.7

  • proposed schedule at links above, tree is open, please work on blockers
  • may adjust schedule to go for early January release to update users with fix for bug 534090 which affects major updates

Firefox 3.6 Beta Testers

  • approaching 600,000 ADUs
  • getting good feedback through various channels
  • Beta 5 builds are being tested by QA now, targeting a Thursday release unless we get to RC first

Firefox 3.6 Release Candidate

  • we are really, really close to being code-complete (see blocker report)
    • only need 8 more patches, and a tracemonkey merge
  • need all hands on deck for those patches and on incoming nominations
  • if we can go to build today or tomorrow, QA will scrap Beta 5 and we'll release RC to the beta audience ASAP

Blocker Report

Firefox 3.6 RC Code Completion

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

Browser / Front End

(Progress reports every weekend on Planet Firefox)

  • see our active projects and get involved / propose others
  • mozilla-1.9.3 front end development (see planet firefox for quick overview):
    • Drew's made Places data visible in a content window
    • Blair's tweaking tab match in awesomebar, should land on trunk soon
    • Rob Strong is fixing the updater for unprivileged windows users, and finding wins in JS startup time (see more)

GFX Update

Layout Update

Content Update

  • JavaScript inter-Process Wrappers (benjamn):
    • Refactored to represent each JSObject with an actor pair.
    • frameLoader.attachChildGlobal(node, "propertyName") to create a property on |node| corresponding to the child's global object, thereby exposing the wrapper.
    • Grass-roots support (mrkbap, peterv) for a change in terminology: Cross-Process Object Wrappers (CPOWs)?
    • Look for my patch in bug 516522 at the first light on the fifth day (end of this week).

Platform-specific Support Update

JS

Startup Performance

Security

Electrolysis

Tree Management

  • Stopped sending test results to *-Unittest trees. bug 534252 Scraping will need to be turned on as new columns show up.
  • Enabled mochitest-ipcplugins tests on m-c, places, tracemonkey bug 530522
  • Turned on optimized and debug packaged tests on tracemonkey bug 524176

Roundtable

  • Need to discuss adding a null deref to make add-ons fail early, i.e., Relevant Knowledge uses the a11y API in a non-threadsafe way. We should block the dlls, but also keep add-on developers from using this in a way that will eventually crash. The problem is we don't know how many add-ons this will break (and will it matter?). Also, is there a patch ready to make this happen? If not, can we get one ready so that we are prepared to pull the trigger? Peterv has the details. (damons)