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

Jump to navigation Jump to search
(New page: <small>« previous week | index | next week »</small> '''Mozilla 2 ...)
 
Line 19: Line 19:
* XPCOMGC status== Followups ==
* XPCOMGC status== Followups ==


== Additional Work List ==
== 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
** Removal of XPConnect
** 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
 
* 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
419

edits

Navigation menu