Mozilla 2/StatusMeetings/2008-01-09: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(More stuff)
Line 13: Line 13:


* ActionMonkey status: [[JavaScript:ActionMonkey]]
* ActionMonkey status: [[JavaScript:ActionMonkey]]
** bsmedberg is generating builds for comparative perftests
** bsmedberg is generating builds for comparative perftests [https://mail.mozilla.org/pipermail/mozilla2-devel/2008-January/000028.html results]


== Updates ==
== Updates ==


* XPCOMGC status== Followups ==
* XPCOMGC status== Followups ==
== Discussion ==
* Schedule for mozilla-central builds, unit test machines, perftest machines
* Schedule for "random branch X" build/unit/perftest


== Work List ==
== Work List ==

Revision as of 19:01, 9 January 2008

« previous week | index | next week »

Mozilla 2 Meeting Details

  • Wednesdays - 11:00am Pacific, 2:00pm Eastern, 19:00 UTC
  • Mozilla Building S - <script> conference room
  • 650-903-0800 or 650-215-1282 x91 Conf# 217 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 217 (US)
  • irc.mozilla.org #mmgc for backchannel

Open Action Items

Updates

  • XPCOMGC status== Followups ==

Discussion

  • Schedule for mozilla-central builds, unit test machines, perftest machines
  • Schedule for "random branch X" build/unit/perftest

Work List

  • Big, invasive, destabilizing changes. These are the sort of tasks that don't respond well to compression (e.g. throwing more people at it) and touch large pieces of the code and/or can destabilize other parts of the development. These are the sort of changes that once landed into the mainline development tree can become the long-pole for release and are difficult to unwind. From the Moz2 meetings it appears the following are in this category:
    • mmGC (including XPCOMGC) *already underway*
    • Exception support *already underway for tooling at least*
    • deCOM
    • Taramin JIT replacing SM *already underway*
    • Better threading support in the core layout engine
    • Centralized security checks
    • Major GFX pipeline changes
    • Protected mode
  • Medium sized, significant in impact changes. These are non-trival, but better isolated. Easier to turn off or backout. Things such as:
    • XBL2
    • Frame construction cleanup
    • Inline re-flow
    • XUL box Model
    • Treaded parsing
    • Threaded image decoding
    • Fewer restarts (e.g. protected extension installs, etc)
    • Features needed for UE
    • UE improvements
    • l10n infra
    • fast-path DOM
    • Clean-up event handling
    • Removal of obsolete APIs
  • Smaller, isolated changes. These are smaller, easy to turn off, or don't impact other critical paths:
    • Worker threads
    • Video
    • Minor CSS improvements
    • Jail tag
    • SVG animation
    • SVG fonts
    • Tabs between windows
    • UE improvements
Retrieved from "https://wiki.allizom.org/index.php?title=Mozilla_2/StatusMeetings/2008-01-09&oldid=79472"