Platform/2009-07-07

From MozillaWiki
Jump to navigation Jump to search

« previous week | index | next week »

Notices / Schedule

Firefox 3.0.12

  • built, being tested
  • shipping to beta next Tuesday

Firefox 3.0.13

  • blocker list this week, mostly complete
  • code freeze in ~1 month
  • opening for landings on Wednesday

Firefox 3.5

  • Over 17 MILLION downloads so far!

Firefox 3.5.1

  • aiming for builds early next week
  • blocking1.9.1.1 and approval1.9.1.1 flags should be used
  • goal of this release should be a quick-turnaround that:
    • topcrash fixes, security/stability patches
    • narrow scope, small changes
    • contrary to some reports on the Internet, this is the usual process for Firefox and software releases; the 3.5 release was strong, stable and solid, and feedback has been extremely positive. Near the end of the release we become extremely conservative about patches to accept; the 3.5.1 release is a quick update to fold in some patches that came up late in the 3.5 release cycle.

Blocker Report

Gecko 1.9.1.1 / Firefox 3.5.1

Browser / Front End

GFX Update

  • bug 753 work continues apace, with several people building on it.
    • If you are doing work that depends in any way on imgIContainer, gfxIImageFrame, nsIImage, you should base them on bug 753.
  • Decode-on-draw work is happening in bug 435296.
  • Jeff's working on an event profiler that has shown some bugs in imagelib; once those are resolved there will undoubtedly be others.
  • #4 topcrasher bug 470487 fix should now be possible that nsWindow refactoring has landed. There have been very few, quite easy to fix regressions from that refactoring.

Layout Update

  • Nothing major to report since last week
  • SVG/MathML in HTML5 parser rocks
  • HTML5 parser creates giant text nodes, should raise priority of work on performance of layout of very large text nodes

Content Update

  • HTML5 parser landed! (preffed off -- about:config pref is "html5.enable")
  • peterv's slimwrappers ready to land (modulo fixing an existing leak that was triggered by this work)
  • bent got the test plugin to draw when running out of process.
  • Lots of awesome plugin code simplification going on (Josh).
  • LiveConnect removal patch up for review.

Mac OS X Update

  • Steven Michaud fixed major OnStopFrame crasher, bug bug 499600.
  • Markus Stange is very close to having a completed patch for fullscreen in 1.9.2, bug 420491.
  • 64-bit Mac OS X port blocked on gfx bug 493280.
  • Cocoa NPAPI event model coming along, part of it landed, maybe 70% complete at this point.

JS

  • looked some at Google's Sputnik ES3 testsuite
    • none of our existing failures are too serious
    • some errors are codified in ES5
    • a large number of existing failures can be tracked to giving native functions (those built into ES5 itself) .prototype
    • many also due to reading all input as ASCII when Sputnik expects UTF-8, see bug 495970 and bug 501265, probably will switch to read input as UTF-8 for simplicity
    • work on bugfixes probably not particularly high-priority, will keep an eye on things as UTF-8 and similar bugs are fixed to clear out the low-hanging fruit

Static Analysis

  • Dan Witte will be working on static analysis for code cleanup, performance, and correctness improvements
  • for instance, bug 502775, bug 172937, and more seriously JS GC safety - bug 421934
  • suggestions for analysis passes we could use are welcome

Security

Fuzz-testers Martijn Wargers and Paul Nickerson are visiting Mountain View this week. We'll be scheduling meetings with lots of groups, such as the people working on the HTML5 parser.

There might be areas that need fuzzing that we're not aware of. If you need something fuzzed, find us near the QA area this week!

Electrolysis

Phase I completed. Repository is in place and builds on Windows/Linux.

cjones still work on minor protocol issues and bsmedberg hooking up automated ipdl generation.

bent working on xpcshell extensions that will allow scripting the remote process for testing and prototyping.

bsmedberg doing local buildbots until RelEng can hook up a full project... reporting to tinderbox.

Tree Management

Roundtable (both topics deferred to next week)

  • triaging blocking nominations earlier in the cycle? (dbaron)
    • getting regressions fixed when people still remember the code that caused them
    • having a smaller pile at the end of the cycle
    • keeping mozilla-central in more-shippable state
  • Can we use a multi-state flag for blocking-1.9.2? Proposed states (bsmedberg):
    • ?
    • -
    • next alpha
    • last alpha
    • beta
    • final