Platform/2010-06-22

« previous week | index | next week »

Notices / Schedule

• Firefox 3.6.4 and 3.5.10
  • Will be released today @ 1:00 pm PST
  • Crash stats issue was likely a stuck git lock when pushing the no-throttle config, which was later cleared on the next git push, unthrottling crash processing

• Firefox 3.6.6 and 3.5.11
  • Initial schedule for Firefox 3.6.6 and 3.5.11 is at Releases/Firefox_3.6.6
    • Please email feedback to clegnitto@mozilla.com
  • Code freeze for both is this Friday, 2010-06-25 @ 11:59 pm PST
    • If you have a blocking bug that can't make this please email clegnitto@mozilla.com or release-drivers@mozilla.org.

• mozilla-2.0 branch, and changes in binary compatibility policies: The branch from which FF4 will be delivered will be called "mozilla-2.0", with a Gecko version of 2.0. Along with this change, we will be moving to a narrower set of binary (native code) compatibility promises for future releases. A quick summary:
  • Between micro/maintenance releases, such as 2.0.1 to 2.0.2, our policy remains unchanged: no incompatible changes to native-code interfaces except as a last resort when predicated by a security requirement.
  • Between minor or major releases, such as 2.0.x to 2.1.x or 1.9.x to 2.0.x, native-code interface compatibility is not guaranteed, even for interfaces that were previously considered FROZEN: providers of native code components, and embedders who use native-code interfaces, will at least need to recompile. We will endeavour to provide a smooth migration strategy for cases where source compatibility is not feasible, and we will also work to ensure that extension authors which rely on native components can support at least two adjacent incompatible Gecko versions in the same package.
  • JSAPI, NSPR, NSS and other currently-linkable libraries may disappear into libxul, and extension authors should avoid linking against them. XPCOM and interfaces expressed in XPCOM will continue to be available, subject to the above; specific interfaces may change between minor or major versions, including changes in semantics as well as implementation details.
  • Scripted interface compatibility with the platform will be maintained aggressively, though we recommend that, for Firefox 4 and beyond, extension authors use the Jetpack APIs where feasible. (Where not feasible, please submit a JEP!)
  • JS-ctypes is the recommended way to interface between extension JS code and custom or OS-provided native code.

Blocker Report

• Firefox 3.6.6
  • 36 open blockers, please get in by this Friday, 2010-06-25 @ 11:59 pm PST

• Firefox 3.5.11
  • 18 open blockers, please get in by this Friday, 2010-06-25 @ 11:59 pm PST

Browser / Front End

• New popup notification system landed, Geo notifications converted to use it (bug 398776)

• (PENDING REVIEW) Create style panel for web page inspector bug 560692
• (PENDING REVIEW) Create DOM Panel for inspecting DOM nodes and their properties bug 561782

• New Theme: Critical Beta 1 Bugs:
  • Drawing in titlebar has patches that Jim needs review on - bug 513162
  • Bookmarks Menu Button - bug 544817
  • Tabs-on-top by default for Windows - bug 571992

• New Theme: Highly Desired Beta 1 Bugs:
  • Mac Theme Bugs bug 547787, bug 559033, bug 559034,

If anyone can lend a hand with reviewing these, that would save Dão and other very busy reviewers some work. If these don't get reviewed and landed by tomorrow, Mac beta 1 will ship without any UI updates, which would make everyone sad. (contact limi or shorlander if you want to help!)

Layout Update

• SVG Animation backwards seeking implemented (birtles)
• Amazing -moz-element work (mstange)
• Lots of editor bugfixing (ehsan)

Electrolysis

• Initial multi-process jetpack enabling patch ready to land
  • Additional API changes are needed to provide "evalInSandbox" facilities
• Electrolysis branch close to landing, bz finalizing reviews, jduell working on merge conflicts, jmaher revising mochitest patch based on comments from smaug

Tree Management

• No more CentOS unit test coverage on m-c. announcement
• Use VC9 on Win64 until jemalloc support for VC10 gets cleared out