|
|
| Line 3: |
Line 3: |
| =e10s Update: '''April 8'''= | | =e10s Update: '''April 8'''= |
| ==Executive Summary== | | ==Executive Summary== |
| * Overall, the phase of the project we currently in is best described as Convergence. For Firefox 47, the most likely scenario will be that we continue to conduct A/B Experiments in our beta channel until we can [https://bugzilla.mozilla.org/show_bug.cgi?id=1259512 lower our rate of main process, content, and Plugin crashes]. Our latest A/B experiment derived data set indicates we have work to do on stability before we're ready to ship to beta. We are, however, hitting our goals in many areas of our [https://wiki.mozilla.org/Electrolysis/Release_Criteria release criteria] such as Page Load, Startup/Shutdown time, and Scrolling. We still have work to do in areas such as UI Smoothness, Plugin Jank, Memory Usage, and GFX Performance but not to the level that would necessarily block beta. We have made excellent progress in our cadence of deploying A/B experiments and quickly ascertaining the data so we have hit a place where we are tightly coordinated and people are empowered with the right data to move on issues swiftly. Another important thing to note is that we are currently using the System Add-On to deploy our A/B experiments so we are testing the mechanism we designed to ship e10s rather than using experiment code. The current experiment (add-ons + ally = no, apz= yes) will end later this week, in time for Beta 7 and we will have updated results soon thereafter. | | * The biggest news this week is that Product has signed off on APZ being enabled when e10s is enabled. User-visible scrolling is much better with APZ than without for most cases. |
| | |
| | * For Firefox 47, the most likely scenario is still that we continue to conduct A/B Experiments in our beta channel until we can [https://bugzilla.mozilla.org/show_bug.cgi?id=1259512 lower our rate of main process, content, and Plugin crashes]. IF, the crash rate lowers thanks to the stability fixes/uplifts that have happened as of late, we may be able to extend the experiment for a longer period of time. We will have the final plan by 04/15. Our goal is to expose as many of the eligible population for as many weeks as possible in order to collect a larger data set of telemetry and crash data and to hopefully see a higher return on bug filing related to issues people see. Our latest A/B experiment derived data set indicates we have work to do on stability before we're ready to ship to beta. We are, however, hitting our goals in many areas of our [https://wiki.mozilla.org/Electrolysis/Release_Criteria release criteria] such as jank and scrolling. We still have work to do in areas such as Startup/Shutdown time, UI Smoothness, Plugin Jank, Memory Usage, and GFX Performance but not to the level that would necessarily block beta. |
|
| |
|
| * The team has shifted to burning down M9's [https://wiki.mozilla.org/E10s/Status/m9]. M9 tickets need to hit zero before we're ready to do our cohort release for GA. M9 is focused on fixing issues derived from our Telemetry A/B experiments such as top crashes, regressions, and backlog items deemed to be blockers by product. We have hit a stage where a portion of the M9's are the responsibility of teams outside of the e10s team so we will be rolling those tickets into central triage managed by RelMan to help with load balance.
| | With the approach of Firefox 47 merging to Beta on April 25, quality and market readiness remain our central focus. |
| | |
| *With the approach of Firefox 47 merging to Beta on April 18, quality and market readiness remain our central focus.
| |
|
| |
|
| ==Why yellow? e10s is designated 'yellow' or 'at risk' because: == | | ==Why yellow? e10s is designated 'yellow' or 'at risk' because: == |