Mozilla 2/Work List

See the short template and the detailed template.

• 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*
  • "Strings" -- sharing strings with JS or moving to STL, moving to UTF8, sanifying the existing string classes
  • 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
  • out-of-memory handling -- figure out how to do OOM handling, allocator hooks to free up memory, etc.

• 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
  • Threaded parsing
  • Threaded image decoding
  • Fewer restarts (e.g. protected extension installs, etc)
  • Features needed for UE
  • UE improvements
  • l10n infra
  • fast-path DOM
  • EventHandlingCleanup
  • 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
  • Kill liveconnect