E10s/Status/April3: Difference between revisions

From MozillaWiki
< E10s‎ | Status
Jump to navigation Jump to search
Line 3: Line 3:
=E10s Update: '''April 3'''=
=E10s Update: '''April 3'''=
==Executive Summary==
==Executive Summary==
* As of Firefox Release 52 (March 7) [https://sql.telemetry.mozilla.org/queries/972#1659 52.82% of the total release population have e10s].  
* As of Firefox Release 52 (April 3) [https://sql.telemetry.mozilla.org/queries/972#1659 52.82% of the total release population have e10s]. e10s is only to add-on users with web extensions or actively marked compatible by the author. This is the plan of record until 57 which means half of all release add-on users will get e10s...but that percentage should grow as add-on authors migrate to WebExtensions in coming months.  
* As of Beta 53, we still have 50-50 split of control and test. We have determined to re-organize the the control/test split to 10% control and 90% test.
* e10s for [https://wiki.mozilla.org/E10s#Add-ons_Schedule Firefox 53 is on track].  
* The goal of 53 Beta and Release is to allow e10s to expand to all users, unless they have add-ons marked specifically MPC=False (not multiprocess compatible). See the full update from Shell, [https://wiki.mozilla.org/Firefox/AddOns/Status/current#Schedule here].
* e10s-multi is enabled as of Firefox 54 Nightly, now with 4 content processes enabled. We are on track for enabling e10s-multi with 4 content processes on [https://bugzilla.mozilla.org/show_bug.cgi?id=1304546#c1 Firefox 54 Aurora]. We are also working on the [system add-on changes for an experiment in Firefox 54 Beta 1https://bugzilla.mozilla.org/show_bug.cgi?id=1349363].  
* e10s-multi is enabled as of Firefox 54 Nightly, now with 4 content processes enabled. We are on track for enabling e10s-multi with 4 content processes in Aurora. A plan for Beta 54 experiments are currently work in progress.
* Our forecast for the engineering schedule tracks to being MVP as of 55 and we are working to uplift as much as possible to 54 with an eye towards shipping in 54 so long as we meet or exceed our release criteria (we are aiming for release 55 for initial roll-out, if we are able to activate multi for some percent of the release population for 54, it will be a happy surprise).
* Our forecast for the engineering schedule tracks to being MVP as of 55 and we are working to uplift as much as possible to 54 with an eye toards shipping in 54 so long as we meet or exceed our release criteria.


=={{mok}} E10s-Multi==
=={{mok}} E10s-Multi==

Revision as of 23:22, 3 April 2017

Green-sm.jpg


E10s Update: April 3

Executive Summary

  • As of Firefox Release 52 (April 3) 52.82% of the total release population have e10s. e10s is only to add-on users with web extensions or actively marked compatible by the author. This is the plan of record until 57 which means half of all release add-on users will get e10s...but that percentage should grow as add-on authors migrate to WebExtensions in coming months.
  • e10s for Firefox 53 is on track.
  • e10s-multi is enabled as of Firefox 54 Nightly, now with 4 content processes enabled. We are on track for enabling e10s-multi with 4 content processes on Firefox 54 Aurora. We are also working on the [system add-on changes for an experiment in Firefox 54 Beta 1https://bugzilla.mozilla.org/show_bug.cgi?id=1349363].
  • Our forecast for the engineering schedule tracks to being MVP as of 55 and we are working to uplift as much as possible to 54 with an eye towards shipping in 54 so long as we meet or exceed our release criteria (we are aiming for release 55 for initial roll-out, if we are able to activate multi for some percent of the release population for 54, it will be a happy surprise).

[ON TRACK] E10s-Multi

  • The team is currently focused on correctness, measuring performance and memory, and Scaling to 4 Processes. You can read more about what this means in the e10s-multi wiki. Basically, we are working hard so multi can ride the trains.
  • The E10s-Multi plan is taking shape: our current forecast predicts that engineering MVP will be complete before the end of Firefox 55. We are currently 80% complete.
    • We have one hard dependency bug 1346247 we need to land before we can enable on Aurora, and one nice-to-have bug 1293277.
    • Determining what Beta experiment design will need to be and making sure any new engineering work required for the System Add-On is defined is currently in progress and should be complete by the end of March 24th.
    • Creating a detailed week-by-week release plan is a work in progress.
    • Final approval on release criteria and making sure any new telemetry requirements are filed.
    • Creating a test plan is assigned and currently in progress.

[ON TRACK] RTL Support, Touchscreen Support, A11y

  • E10s support for RTL versions of Firefox on Linux is still planned for Firefox 52 (Windows and Mac shipped in Firefox 50).
  • A11y and touchscreen support has landed in 51. We are still targeting 52 for release for Windows 8 and Windows 10.
  • The plan is to ship A11y for Windows for Firefox 55.