Mozilla 2/StatusMeetings/2008-04-16

From MozillaWiki
Jump to: navigation, search

« previous week | index | next week »

Mozilla 2 Meeting Details

  • Wednesdays - 11:00am Pacific, 2:00pm Eastern, 18: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)
  • #mmgc for backchannel

Status Reports

  • jimb
  • dmandelin
  • taras
  • bsmedberg
  • shebs
    • no progress, on breakpad this week
  • jorendorff


  • opening mozilla-central for general checkins is tracking bug 422754
    • unit tests... status?
    • debug+leak... joduinn working on them
      • linux, win32 waiting for VM space
      • mac buildbot slave connected last night; should be building soon
  • Identifying "working groups" post-1.9 (damons)
    • Need to be able to answer the question "Who's working on what?"
    • Not set in stone... more a question of status and resources.

If time, some thought points for mozilla-central breakage: discussion points

  • Rework nsIFrame inheritance (no longer inherit from nsISupports)
    • bug 396185
    • This makes XPCOMGC analysis reasonable
    • doesn't break frozen APIs
    • only requires changes for extensions which use frame objects, which should be few and far-between
  • XPConnect-wrapped-XPCOM objects must implement classinfo
    • Significantly reduces the number of code paths in xpconnect
    • allows for optimization such as early static prototyping of objects
    • could break extensions or change their behavior:
      • No more QI needed on any JS objects; they have all the reflected XPCOM properties automatically
      • If JS implements XPCOM components which are reflected back into JS, they will need to implement classinfo
  • mozilla:RefPtr for thebes
  • QI rewrite
    • bug 391275
    • breaks nsISupports (frozen API)
    • perf win (5%)
  • Turn off OJI (already done on mozilla-central)
    • breaks compatibility with older JREs
  • Disable xpconnect idispatch scripting
    • right now we assume nsISupports is binary-compatible with IUnknown. Have to do this before we change nsISupports in any way
  • no-fail OOM handling
    • bug 427099
    • Perf/codesize/code complexity win
    • Requires "intrusive" automatic rewrite of the codebase... need confidence in rewriting correctness