Platform/2009-08-18: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 55: Line 55:


=== Electrolysis ===
=== Electrolysis ===
Necko:
* Close to having necko IPC protocol hooked up and initialized
* Some high-level design progress (from conversation with BZ)
** IPC probably "main chrome thread <-> content process", not "Socket transport thread <-> content process"
** Probably use "if(ContentProcess)" within existing necko code, rather than create new set of classes for Content-side necko.
* Issue: which protocols (network; file?) need IPC?
* Issue: goodbye standalone necko?
* Set up design discussion for workweek


=== Tree Management ===
=== Tree Management ===

Revision as of 17:39, 18 August 2009

« previous week | index | next week »

Notices / Schedule

Firefox 3.0.13

Firefox 3.5.2

Firefox 3.6a1

Blocker Report

Gecko 1.9.2 / Namoroka

Browser / Front End

GFX Update

  • Decode-on-draw is getting close to review-worthy. bug 435296
  • Mark Steele starting work on WebGL implementation.

Layout Update

  • 24 open blocking1.9.2+ bugs in Layout
    • 7 are regressions from ireflow (there's also 1 in Widget)
    • 1 is a regression from compositor phase 1 (there's also 1 in Plugins)
  • dholbert making progress on code to be shared between SMIL animation of CSS and CSS transitions (bug 504652)
  • first parts of zwol's frame poisoning work now landed on mozilla-central (but not the main patch) (bug 497495)
  • roc's scroll optimization patch landed on mozilla-central and 1.9.2 (bug 507334)

Content Update

  • 1.9.2:
    • 13 open blocking1.9.2+ bugs in Content
    • 12 nominations, will triage...
  • Investigating twitter bug bug 510985.
  • Making progress on multi process networking.
  • peterv is making progress on ibench numbers, but not clear how heavily to invest there.
  • HTML5 parser work ongoing, including some 1.9.2 blockers there.
  • First pass at a Jetpack security model done.

Platform-specific Support Update

JS

Startup Performance

Security

Electrolysis

Necko:

  • Close to having necko IPC protocol hooked up and initialized
  • Some high-level design progress (from conversation with BZ)
    • IPC probably "main chrome thread <-> content process", not "Socket transport thread <-> content process"
    • Probably use "if(ContentProcess)" within existing necko code, rather than create new set of classes for Content-side necko.
  • Issue: which protocols (network; file?) need IPC?
  • Issue: goodbye standalone necko?
  • Set up design discussion for workweek

Tree Management

Roundtable

  • Project metrics charts (timr)
  • Who is allowed to mark approval1.9.2+ ? (dbaron)
  • should we mark the set of bugs that are fixed on mozilla-1.9.2 by virtue of branching as fixed1.9.2+ (beltzner)