Mozilla 2/Work List: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
* 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: | * 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: | ||
** [[XPCOMGC|mmGC (including XPCOMGC)]] - bsmedberg | ** [[XPCOMGC|mmGC (including XPCOMGC)]] - bsmedberg/jst | ||
** [[Mozilla 2/Strings|"Strings"]] -- sharing strings with JS or moving to STL, moving to UTF8, sanifying the existing string classes - bsmedberg | ** [[Mozilla 2/Strings|"Strings"]] -- sharing strings with JS or moving to STL, moving to UTF8, sanifying the existing string classes - bsmedberg | ||
** [[Gecko:DeCOMtamination|deCOMtamination]] - roc (taras) | ** [[Gecko:DeCOMtamination|deCOMtamination]] - roc (taras) | ||
Revision as of 23:46, 27 June 2008
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) - bsmedberg/jst
- "Strings" -- sharing strings with JS or moving to STL, moving to UTF8, sanifying the existing string classes - bsmedberg
- deCOMtamination - roc (taras)
- Mozilla 2/Tracing JIT - brendan, Andreas Gal, others
- Mozilla 2/Centralized security checks - mrbkap/jst/brendan
- Mozilla 2/Protected mode - jmathies/rstrong
- Mozilla 2/Memory - out-of-memory handling - figure out how to do OOM handling, allocator hooks to free up memory, etc. - bsmedberg (jasone)
- GFX - 3D Acceleration - vlad
- 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
- GFX - Compositor -- one widget per window, frame rate controls
- GFX - Software Rendering Performance
- SVG - Maintenance
- GFX - Mobile
- GFX - Cleanup -- general cleanup, removing old interfaces
- Smaller, isolated changes. These are smaller, easy to turn off, or don't impact other critical paths:
- Worker threads
- Mozilla 2/Video and Audio
- CSS improvements
- Jail tag
- querySelector / querySelectorAll (bug 416317)
- SVG - Animation
- SVG - Fonts
- SVG - Filters
- Tabs between windows
- UE improvements
- Mozilla 2/Kill LiveConnect - jst
- Mozilla 2/GFX/ImageLib work - Image decode-on-draw, threaded decoding
- SVG - Use-as-image
- Mozilla 2/Canvas 3D
- Rework arrays in IDL