E10s/Status/Sept2: Difference between revisions

From MozillaWiki
< E10s‎ | Status
Jump to navigation Jump to search
(Created page with "thumbnail|left<br> =e10s Update: '''September 2'''= ==Executive Summary== * With the hotfix/48.0.2 release out the door and given that E10s enabled for...")
 
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[File:Green-sm.jpg|thumbnail|left]]<br>
[[File:Green-sm.jpg|thumbnail|left]]<br>


=e10s Update: '''September 2'''=
=E10s Update: '''September 2'''=
==Executive Summary==
==Executive Summary==
* With the hotfix/48.0.2 release out the door and given that E10s enabled for Firefox 48 continues to be green, we have decided to increase activation for 100% of our eligible population {{bug|1299247}}. We have hit [https://sql.telemetry.mozilla.org/dashboard/client-count-firefox-e10s-release- 1.86M DAU on August 30] and [https://sql.telemetry.mozilla.org/queries/613/source stability dashboard our crash rate remains within range of our release criteria]. So far, our [https://sql.telemetry.mozilla.org/queries/618#1037 engagement ratio] actually looks better for the E10s group but given that our release population has been fairly skewed, we need more time to draw a definite conclusion. It's worth noting that the we're trending in the right direction. If you have any questions about this data please just ping me or in #e10s.  
* '''As of Tuesday, Sept 6''', we have hit [https://sql.telemetry.mozilla.org/dashboard/client-count-firefox-e10s-release- 20M DAU] and [https://sql.telemetry.mozilla.org/queries/613/source stability dashboard our crash rate remains within range of our release criteria].  
* '''How are things looking for Add-Ons in Firefox 49 Beta?''' So far, really good. There isn't any data that indicates we can't enable E10s with users for our [https://docs.google.com/spreadsheets/d/1zE1TNV0z6gaYgugBAns3XXDexLDHAa2Dmj0EVQIg8tc/edit#gid=0 Whitelisted Add-Ons] and for Add-Ons created as [http://arewee10syet.com/ WebExtensions].  
* Increasing the population impacts our Engagement Ratio data; we need to give the MAU data time to catch up since we've deployed the increase. More on this next week.
* The top issue we are investigating is {{Bug|1300411}} - user reports excessive load spinning when switching tabs with e10s in 48.0.2 release. Here is what we know:
** There are 3 individual reports. One of which that is the most reproducible seems related to an issue with {{bug| 1279086}} google docs. Testing is needed to confirm.
** 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}}.  
* '''How are things looking for Add-Ons in Firefox 49 Beta?''' STILL GREEN. There isn't any data that indicates we can't enable E10s with users for our [https://docs.google.com/spreadsheets/d/1zE1TNV0z6gaYgugBAns3XXDexLDHAa2Dmj0EVQIg8tc/edit#gid=0 Whitelisted Add-Ons] and for Add-Ons created as [http://arewee10syet.com/ WebExtensions].


=Next Steps=
=Next Steps=
Line 11: Line 15:


==Add-Ons + WebExtensions==
==Add-Ons + WebExtensions==
* So far everything is looking good for add-ons + e10s in the 49 experiments
* Everything is looking good for add-ons + e10s in the 49 experiments and as stated above, we will ship 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 [https://docs.google.com/spreadsheets/d/1OFYrrvAFg8y1mZOEbuIR1axxtV8eul_be6ad9fe8JB0/edit?usp=sharing here].
* General roll-out plan for including extensions is [https://docs.google.com/spreadsheets/d/1OFYrrvAFg8y1mZOEbuIR1axxtV8eul_be6ad9fe8JB0/edit?usp=sharing here].


==A11y==
==A11y + Windows 8 Touchscreen Support==
* A11y and touchscreen support has landed in 51! \o/  
* A11y and touchscreen support has landed in 51! \o/  
* We're also looking into Windows touchscreen/a11y compat, see more information as the plan is taking shape, [https://public.etherpad-mozilla.org/p/a11y+e10s here].
* We're also looking into Windows touchscreen/a11y compat, see more information as the plan is taking shape, [https://public.etherpad-mozilla.org/p/a11y+e10s here].


==RTL Support==
==RTL Support==
* E10s support for RTL versions of Firefox on Windows and Mac is targeted for Firefox 50.
* E10s support for RTL versions of [https://bugzilla.mozilla.org/show_bug.cgi?id=1033483 Firefox on Linux] is TBD.


==E10s on Windows XP==
* We are making a concerted effort to support E10s on Windows XP.
* Details can be found, here: {{bug|1296279}}


==Automated tests==
==Automated tests==
Line 42: Line 52:
|8-02 || 51 default || 50 default || 49 Possible Rollout (add-ons + ally = no) || 48  Rollout (add-ons + ally = no)  
|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)  
|9-13 || 52 default || 51 default || 50 Possible Rollout (add-ons + ally = no) || 49 Rollout (known good add-ons = yes, ally = no)  
|}
|}

Latest revision as of 19:41, 9 September 2016

Green-sm.jpg


E10s Update: September 2

Executive Summary

  • As of Tuesday, Sept 6, we have hit 20M DAU and stability dashboard our crash rate remains within range of our release criteria.
  • Increasing the population impacts our Engagement Ratio data; we need to give the MAU data time to catch up since we've deployed the increase. More on this next week.
  • The top issue we are investigating is bug 1300411 - user reports excessive load spinning when switching tabs with e10s in 48.0.2 release. Here is what we know:
    • There are 3 individual reports. One of which that is the most reproducible seems related to an issue with 1279086 bug 1279086 google docs. Testing is needed to confirm.
    • 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.
  • How are things looking for Add-Ons in Firefox 49 Beta? STILL GREEN. There isn't any data that indicates we can't enable E10s with users for our Whitelisted Add-Ons and for Add-Ons created as WebExtensions.

Next Steps

  • 09/12: Bug tracking and Team RASCI transition
  • 09/19-20: Retrospective to be scheduled

Add-Ons + WebExtensions

  • Everything is looking good for add-ons + e10s in the 49 experiments and as stated above, we will ship 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 + Windows 8 Touchscreen Support

  • A11y and touchscreen support has landed in 51! \o/
  • We're also looking into Windows touchscreen/a11y compat, see more information as the plan is taking shape, here.

RTL Support

  • E10s support for RTL versions of Firefox on Windows and Mac is targeted for Firefox 50.
  • E10s support for RTL versions of Firefox on Linux is TBD.

E10s on Windows XP

  • We are making a concerted effort to support E10s on Windows XP.
  • Details can be found, here: bug 1296279

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.

Multi Process

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

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