E10s/Status/May5

e10s Update: May 6

Executive Summary

• The biggest news this week is that all Release Criteria that has been signed off continues to pass in Firefox 47 Beta. There are no new regressions thus far. This is according to our latest [ https://github.com/vitillo/e10s_analyses/blob/master/beta47-ex1/e10s_experiment.ipynb derived data set] which ran from April 27-May 4. We will run these data sets weekly in order to evaluate performance on an ongoing basis. We have at least 469,350 users with e10s enabled on beta.

• Our #1 risk remains stability. Our crash rates for beta 1 are still higher (27.2) vs. non-e10s (9.2). A full 33% of e10s content crashes in b1 were caused by bug 1255823 which is fixed for b2, so we expect the crash rate for b2 to stabilize around 20. Getting to 20 or below is our stated goal for next week.

With the approach of Firefox 47 Beta 4 on May 10, stability and unearthing important details we need to line up for a staged rollout to GA remains our central focus.

Why yellow? e10s is designated 'yellow' or 'at risk' because:

Stability is our #1 risk to our plan to stay enable for the entire beta cycle in Firefox 47. We also need to continue to make progress on an issue with slow scripts. All other areas of release criteria are looking good.

Next Steps

• 04/10: Firefox 47 Beta 3 Ships
• 05/11: Second derived data set available (2 weeks of data)
• 05/12: Quality check point

Release Criteria

• See the wiki for up-to-date e10s release criteria status

Add-Ons + WebExtensions

• Decision to not have an allow list has been made, we will take a more efficient approach. Only add-ons that have self identified as e10s compliant can be part of the e10s activation audience at first -in addition to all add-ons that are webextensions. See bug 1249060 for more details.
• General roll-out plan for including extensions is here.

Automated tests

• Everything we can have enabled in production is enabled, everything else is enabled on a separate branch called 'Ash'.
• We have all tests be owned
• We would like each directory signed-off by test owners week of 06/05
• We're tracking all the tests and who owns them, here
• We are tracking tests that are running and passing on some platforms, but are disabled on others.From a feature coverage point of view, it's in pretty great shape. There's very little that is disabled both on opt *and* debug on a same platform (meaning that that test is not running on this platform). Look for the "Fully disabled in a platform" entries in this spreadsheet.

A11y

• Proposed technical path to encourage a11y clients to communicate directly with the content process bug 1258839. dbolter is getting some first impressions from clients to see if this is a viable approach.
• We're also looking into Windows touchscreen/a11y compat, see more information as the plan is taking shape, here.

Milestones

We are at the point where we are setting milestones weekly; given the complexity of deliverables, we are using a Trackback Schedule to keep everything organized.

Release Schedule

Date	Trunk	Aurora	Beta	Release
3-07	48 default	47 default	46 A/B Tests	45 off
4-18	49 default	48 default	47 A/B Tests, Possible Rollout (add-ons = ally = no)	46 off
6-07	50 default	49 default	48 Possible Rollout (add-ons + ally = no)	47 off
8-02	51 default	50 default	49 Possible Rollout (add-ons + ally = no)	48 Possible Rollout (add-ons + ally = no)
9-13	52 default	51 default	50 Possible Rollout (add-ons + ally = no)	49 Possible Rollout (add-ons + ally = no)