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

m
Undo revision by Lolth -> Vandalism
(New page: <small>« previous week | index | next week »</small> '''Mozilla 2 ...)
 
m (Undo revision by Lolth -> Vandalism)
 
(6 intermediate revisions by 2 users not shown)
Line 10: Line 10:
__TOC__
__TOC__


== Open Action Items ==
== Discussion ==


* ActionMonkey status: [[JavaScript:ActionMonkey]]
* ActionMonkey stage 4 - unifying the Spidermonkey and tamarin object models
** Tamarin uses UTF8, which could make existing APIs such as JS_GetStringChars difficult
** jimb and jorendorff madly documenting the JSAPI


== Updates ==
* Dynamic analysis: dump the string data size in UTF16/UTF8
* Dynamic analysis: count the number of conversions between short and wide
* Dynamic analysis: autostring buffer-copy counts (are autostrings worthwhile)?
* How many strings exist *only* for conversion?
* Static analysis: if "AString" were immutable, where would we fail?


* XPCOMGC status== Followups ==
== Action Items ==
 
== Discussion ==


* Schedule for mozilla-central builds, unit test machines, perftest machines
bsmedberg to find owners for large work items and hound people for a description of work
* Schedule for "random branch X" build/unit/perftest
** after Build finishes cleanup of beta2 cleanup changes, and gets nightlies running on buildbot also.
** tracking in {{bug|411538}}.
* Schedule for "random branch X" unit/perftest
* Feature Area/Work List [http://wiki.mozilla.org/Mozilla_2/Feature_Proposal templates] more detailed template (for later) [http://wiki.mozilla.org/Mozilla_2/Feature_Plan_Template detailed template]


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


 
Moved to [[Mozilla 2/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*
** "Strings" -- sharing strings with JS or moving to STL, moving to UTF8, sanifying the existing string classes
** [http://wiki.mozilla.org/Mozilla_2/Exceptions 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
** Threaded parsing
** Threaded image decoding
** Fewer restarts (e.g. protected extension installs, etc)
** Features needed for UE
** UE improvements
** l10n infra
** fast-path DOM
** [http://wiki.mozilla.org/Mozilla_2/EventHandlingCleanup 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
350

edits