e10s Update: July 1

Executive Summary

• The biggest news is that the stability release criteria for Beta 48 has been signed off on [1]. Slow script count is also within release criteria target.
• We are also at 0 M9's (and have been) for a few weeks
• As of this week, 569K users have been exposed to e10s in Beta 48.
• Given that we have met all of our release criteria and we have not regressed since 47 beta, the project is now designated 'green' or 'on track' to ride the trains to GA and be gradually rolled out (1% at start) to eligible users (41% of total population) or about 800K users for the first 3 weeks.
• So what's the release plan? We are working on a day-by-day snapshot of the activities that have to occur once Firefox 48 goes to GA. This is basically a small 'throttle team' who will be at helm of throttling e10s up or down (or disabling). This is driven by RelMan but will be supported by e10s subject matter experts so that decisions can be made quickly. You can refer to these docs for more info and WIP details: http://bit.ly/29mIbXs and

Next Steps

• 05/20: Firefox 47 Beta 7 Ships
• 05/25: Fourth derived data set available (4 weeks of data)
• 05/24: Release plan review

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

• We are at about 90% [https://wiki.mozilla.org/Electrolysis/Test_Coverage 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.

A11y

• It's looking like the initial API support will land in 50

• 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