Revision as of 23:28, 5 August 2016

e10s Update: August 5

We have shipped to 1% of of our eligible (41% of total) population \o/ and plan to increase the percentage to 10% as of August 15.
The data we have in terms of crash stats is looking healthy and there are not any major issues that have surfaced since we shipped; have have a couple of ride alongs for 48.0.1 which is being planned to handle a unrelated crash.
The telemetry data we are able to collect indicates we are on track for our intended number of users; we won't have exact numbers for about a week. We had numbers initially because the number of users was low; now that the numbers are higher, there is a delay in obtaining the data.
We had three blog posts:

After 48 goes GA what happens with the team/incoming bugs? The e10s RASCI doesn't change until September 12th. We will continue to nom and tag tickets as we have thus far. The same group will be making decisions throughout the 48 cycle. We will be encouraging module owners and originators to scrub the backlog of meta bugs to be sure things are prioritized correctly in parallel. After September 12, the e10s-tracking flag will be deprecated and the mainline Firefox tracking flag(s) will be used by RelMan. There will be e10s keywords bug 1290509 we can tag tickets with to monitor the overall flow of e10s-related tickets. The "e10s RASCI" will transition from the current team as it stands and some of us will be working on e10s-multi. Operationally, responsibility shifts to the add-ons team to monitor Firefox 49 experiment feedback and make decisions regarding shipping add-ons in an e10s world. Shell Escalante is the EPM for this effort. Elan will shift focus to helping more with e10s-multi. Stay tuned for a more complete RASCI during this transition.

It's looking like the initial API support will land in 50
We are NOT targeting 50 for GA but rather 51
We're also looking into Windows touchscreen/a11y compat, see more information as the plan is taking shape, here.

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.

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-13	52 default	51 default	50 Possible Rollout (add-ons + ally = no)	49 Possible Rollout (known good add-ons = yes, ally = no)

@@ Line 8: / Line 8: @@
 * We had three blog posts:
 ** [https://blog.mozilla.org/futurereleases/ Future of Firefox]
+** [https://blog.mozilla.org/blog/2016/08/02/exciting-improvements-in-firefox-for-desktop-and-android/ Mozilla GA Blog]
+** [https://blog.mozilla.org/addons/2016/08/02/multi-process-firefox-and-add-ons-a-call-to-action/ Add-Ons Blog]
 * '''After 48 goes GA what happens with the team/incoming bugs?''' The e10s RASCI doesn't change until September 12th. We will continue to nom and tag tickets as we have thus far. The same group will be making decisions throughout the 48 cycle. We will be encouraging module owners and originators to scrub the backlog of meta bugs to be sure things are prioritized correctly in parallel. After September 12, the e10s-tracking flag will be deprecated and the mainline Firefox tracking flag(s) will be used by RelMan. There will be e10s keywords {{bug|1290509}} we can tag tickets with to monitor the overall flow of e10s-related tickets. The "e10s RASCI" will transition from the current team as it stands and some of us will be working on e10s-multi. Operationally, responsibility shifts to the add-ons team to monitor Firefox 49 experiment feedback and make decisions regarding shipping add-ons in an e10s world. Shell Escalante is the EPM for this effort. Elan will shift focus to helping more with e10s-multi. Stay tuned for a more complete RASCI during this transition.