Firefox/AddOns/Status/current: Difference between revisions

m
Line 7: Line 7:
**No significant impact on Stability based on add-ons and e10s has been seen.
**No significant impact on Stability based on add-ons and e10s has been seen.
**users with add-ons not in the target group will continue to work and just not receive the e10s update
**users with add-ons not in the target group will continue to work and just not receive the e10s update
*50 Beta [[https://bugzilla.mozilla.org/show_bug.cgi?id=1297755 Target populations] for e10s activation are webextensions and all add-ons the authors manually marked as compatible (MPC=True).
*50 Beta [https://bugzilla.mozilla.org/show_bug.cgi?id=1297755 Target populations] for e10s activation are webextensions and all add-ons the authors manually marked as compatible (MPC=True).
**roughly 6.41% of Beta users qualified: 56,000 in test group and 56,000 in control group
**roughly 6.41% of Beta users qualified: 56,000 in test group and 56,000 in control group
**Listed add-on counts that meet the target population criteria are at the top of [http://arewee10syet.com/ arewee10syet.] ~1900
**Listed add-on counts that meet the target population criteria are at the top of [http://arewee10syet.com/ arewee10syet.] ~1900
*There are 1,007 listed WebExtensions and 11,692 unlisted WebExtensions. The listed ones add up to 2,798,403 ADI
**There are 1,007 listed WebExtensions and 11,692 unlisted WebExtensions. The listed ones add up to 2,798,403 ADI
**If Beta 50 passes [https://docs.google.com/spreadsheets/d/1j1GnKGaMmdHDHccanst8EQC2wSK07pvRnHAWISv5FoA/edit?usp=sharing release criteria], it should not require throttling.
**Releases beyond 50, we will need to look at adapting the targeting system add-on
**First few weeks of Beta 50 have shown no issues created by the add-on/e10s inclusion with [https://sql.telemetry.mozilla.org/dashboard/stability-metrics-for-e10s-add-ons-experiment-beta-49-50-51- Stability] or [https://github.com/mozilla/e10s_analyses/blob/master/beta/50/week1/e10s_experiment.ipynbPerformance].
**First few weeks of Beta 50 have shown no issues created by the add-on/e10s inclusion with [https://sql.telemetry.mozilla.org/dashboard/stability-metrics-for-e10s-add-ons-experiment-beta-49-50-51- Stability] or [https://github.com/mozilla/e10s_analyses/blob/master/beta/50/week1/e10s_experiment.ipynbPerformance].
*In 50 MPC:true was adjusted to also [https://bugzilla.mozilla.org/show_bug.cgi?id=1214824 block CPOW usage] (in addition to shims).  Only a few add-ons that had already used CPOWs directly were excluded for a brief transition period.
**In 50 MPC:true was adjusted to also [https://bugzilla.mozilla.org/show_bug.cgi?id=1214824 block CPOW usage] (in addition to shims).  Only a few add-ons that had already used CPOWs directly were excluded for a brief transition period.
*Releases beyond 50, we will need to look at adapting the targeting system add-on to throttle availability.
**In 49 and 50 - the qualifying number of users was about what we'd want to activated at one time (2-3%).
**Beyond 50 - we expect more like 50-70% to qualify and we do not want to make e10s activation change all at once.


== Release 49 Details ==
== Release 49 Details ==
Confirmed users
1,094

edits