E10s Update: October 3

Executive Summary

As of Oct, we have hit 66.45M MAU. Now that we are in a new Release Cycle, we expect our Engagement Ratio data to catch up by this time next week for 49.0.1
Our crash rate remains within range of our release criteria.
Biggest news is that we enabled E10s with users for our Whitelisted Add-Ons and for Add-Ons created as WebExtensions as of Firefox 49. We are in a similar situation as we were for 48 in that the Release population is skewed in that automatic updates for disabled for Windows users due to a websense crash. We have shipped 49.0.1 today to fix this so we should have a better grasp on how things are going next week.

Investigation continues for bug 1300411 - user reports excessive load spinning when switching tabs with e10s in 48.0.2 release. Here is what we know:
- There are 6 individual reports; engineering is actively engaged with 1-2 people. One of which that is the most reproducible seems related to an issue with 1279086 bug 1279086 google docs. [SV has been able to https://bugzilla.mozilla.org/show_bug.cgi?id=1300411#c42 manually reproduce the issue].
- In order to better surmise the scale of the this issue, we are landing opt-out telemetry probes as of Firefox 49 bug 1301104 and bug 1301435.
- We are also disabling e10s for users who are experiencing the spinner upon opening a new tab. This will be included as a ridealong for the next dot release for 49 (if we decide to ship one).
Another top issue has surfaced this week; we have disabled E10s for the Russian Locale since the crash impacts a popular email site. Once the fix lands, we plan on re-enabling E10s. We would need to ship the fix in a dot release for 49 and is being considered a ridealong at this time.

We shipped Firefox 49 with a set of compatible Add-Ons enabled.
Decision Made: We will continue A/B experiments on Beta and will maintain the same % of the population (50% of eligible).
General roll-out plan for including extensions is here.

A11y and touchscreen support has landed in 51. We are targeting 52 so we can:
- Benefit from the touch events work happening APZ
- Our primary blocker bug 1297549
- We have about 12 issues we would like to fix before rolling out
- Enabling tests
- Optimization work and APZ dependency which is slated for 52
NVDA is the first client we plan on achieving compliance with. We feel that if A11y can work with NVDA, we should be at about 90% of functionality with other, similar clients.

bug 1277831 E10s support for RTL versions of Firefox on Windows and Mac is on trackfor Firefox 50. Softvision has just signed off on RTL support for e10s in their mid-aurora sign-offs.
E10s support for RTL versions of Firefox on Linux is TBD.

We are at 90% Test coverage for all channels. We have touched base with all module owners. Not all of them have signed off specifically but we are calling it within acceptable range for shipping at this point.
Working to get tests enabled for A11y is currently our focus.

Bi-weekly meetings have commenced for e10s-multi, see more info:

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 Rollout (add-ons + ally = no)
9-20	52 default (multi-lands)	51 default	50 Rollout (add-ons = yes + ally = no)	49 Rollout (known good add-ons = yes, ally = no)
11-8	53 default (multi-enabled)	52 (multi =yes)	51 default	50 rollout + known good add-ons