Platform/2010-06-22: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with '<small>« previous week | index | next week »</small> = Notices / Schedule = = Blocker Report = = Brows…')
 
 
(33 intermediate revisions by 18 users not shown)
Line 1: Line 1:
<small>[[Platform/2010-06-15|&laquo; previous week]] | [[Platform|index]] | [[Platform/2010-06-29|next week &raquo;]]</small>
<small>[[Platform/2010-06-15|&laquo; previous week]] | [[Platform|index]] | [[Platform/2010-06-29|next week &raquo;]]</small>


= Notices / Schedule =
= 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 [mailto:clegnitto@mozilla.com 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 [mailto:clegnitto@mozilla.com clegnitto@mozilla.com] or [mailto:release-drivers@mozilla.org 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''':&nbsp;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 =
= Blocker Report =
* '''Firefox 3.6.6'''
** [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking1.9.2:.6%2B%20-status1.9.2:.6-fixed&order=map_assigned_to.login_name,bugs.bug_id 36 open blockers], please get in by this Friday, 2010-06-25 @ 11:59 pm PST
* '''Firefox 3.5.11'''
** [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking1.9.1:.11%2B%20-status1.9.1:.11-fixed&order=map_assigned_to.login_name,bugs.bug_id 18 open blockers], please get in by this Friday, 2010-06-25 @ 11:59 pm PST
* '''Firefox 4 Beta 1'''
** [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking1.9.3:beta1 17 bugs remaining]
** long poles are
*** {{bug|564991}} retain layers (needs reviews)
*** {{bug|513162}} draw in title bar (needs reviews)
*** {{bug|561476}} code review for Feedback XPI, and associated bugs ({{bug|573079}})
*** any others? 64 bit build symbols?


= Browser / Front End =
= Browser / Front End =
* New popup notification system landed, Geo notifications converted to use it ({{bug|398776}})


= GFX Update =
* '''(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}}


= Hardware Acceleration Update =
* New Theme: Critical Beta 1 Bugs:
** Drawing in titlebar on win ({{Bug|513162}})
*** base patches posted (seeking reviews from: smaug, dbaron, bz, vlad), glass desktops will work with these patches.
*** non-glass themed window frame drawing patch is coming along. (Should be posted today, might make friday freeze.)
*** "Move window via glass areas" ({{Bug|555081}}|felipe) will be needed for usability if this is enabled for the beta, currently this is not blocking.
** 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!)
 
= GFX/Hardware Acceleration Update =
 
Hope to turn Direct2D by default soon without regressing startup by too much (minimal for those without sufficient hardware, ~130ms? for those with)
 
Support for accelerated, full-screen video on linux ''just'' landed, please give it a try.


= Layout Update =
= Layout Update =
* Should drop retained layers for beta1: too much risk, still probably a few days away at best
* SVG Animation backwards seeking implemented (birtles)
* Amazing -moz-element work (mstange)
* Lots of editor bugfixing (ehsan)
* Style system performance improvements (bz)


= Content Update =
= Content Update =
* Websockets landed! (wellington, smaug)
* IndexedDB landed but bounced.  Analyzing test failure in record+replay now (bent, sdwilsh)


= Platform-specific Support Update =
= Platform-specific Support Update =
Line 20: Line 78:


= Electrolysis =
= 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


= Startup Performance =
= Startup Performance =
Line 28: Line 90:


= Tree Management =
= Tree Management =
* No more CentOS unit test coverage on m-c. [http://groups.google.com/group/mozilla.dev.tree-management/browse_thread/thread/1cfb8f3314e5c82c# announcement]
* Use VC9 on Win64 until jemalloc support for VC10 gets cleared out
* Twig branches online! [[DisposableProjectBranches]]
* Handy tip for preventing unwanted builds on Try [[Build:TryServerAsBranch#Using_a_custom_mozconfig]]
* mozilla-2.0 infrastructure available late today or tomorrow. Locked down as requested - any idea when people would want to start using?
* Powering off the FF3.0.x machines {{bug|554226}}


= Roundtable =
= Roundtable =
* mozilla-2.0 & binary compat [shaver]

Latest revision as of 18:29, 22 June 2010

« 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
  • 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
  • Firefox 3.5.11

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 on win (bug 513162)
      • base patches posted (seeking reviews from: smaug, dbaron, bz, vlad), glass desktops will work with these patches.
      • non-glass themed window frame drawing patch is coming along. (Should be posted today, might make friday freeze.)
      • "Move window via glass areas" (bug 555081|felipe) will be needed for usability if this is enabled for the beta, currently this is not blocking.
    • Bookmarks Menu Button - bug 544817
    • Tabs-on-top by default for Windows - bug 571992

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!)

GFX/Hardware Acceleration Update

Hope to turn Direct2D by default soon without regressing startup by too much (minimal for those without sufficient hardware, ~130ms? for those with)

Support for accelerated, full-screen video on linux just landed, please give it a try.

Layout Update

  • Should drop retained layers for beta1: too much risk, still probably a few days away at best
  • SVG Animation backwards seeking implemented (birtles)
  • Amazing -moz-element work (mstange)
  • Lots of editor bugfixing (ehsan)
  • Style system performance improvements (bz)

Content Update

  • Websockets landed! (wellington, smaug)
  • IndexedDB landed but bounced. Analyzing test failure in record+replay now (bent, sdwilsh)

Platform-specific Support Update

JS

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

Startup Performance

Security

Breakpad

Tree Management

Roundtable

  • mozilla-2.0 & binary compat [shaver]
Retrieved from "https://wiki.allizom.org/index.php?title=Platform/2010-06-22&oldid=232619"