Firefox/AddOns/Status/current: Difference between revisions

Line 1: Line 1:


=<big>'''Add-ons/e10s Program Status Report'''</big>=
=<big>'''Add-ons/e10s Program Status Report'''</big>=
== Exec Summary/Hot Topics - Nov 30th ==
== Exec Summary/Hot Topics - Dec 4th ==
Since September - listed add-ons increased from ~1/10 (1600) using webextensions or marked multi process compatible to ~1/8th (2,100)
Since September - listed add-ons increased from ~1/10 (1600) using webextensions or marked multi process compatible to ~1/8th (2,100)
<p></p>'''50'''
<p></p>'''50'''
Line 11: Line 11:
**Anecdotal evidence showed noticeable improvements (patches landed in Nightly [https://bugzilla.mozilla.org/show_bug.cgi?id=1309351 Oct 17] & [https://bugzilla.mozilla.org/show_bug.cgi?id=1309350 Oct 24)] and telemetry showed fewer hangs and shorter duration.
**Anecdotal evidence showed noticeable improvements (patches landed in Nightly [https://bugzilla.mozilla.org/show_bug.cgi?id=1309351 Oct 17] & [https://bugzilla.mozilla.org/show_bug.cgi?id=1309350 Oct 24)] and telemetry showed fewer hangs and shorter duration.
'''51'''
'''51'''
*Beta 51 is going to [https://bugzilla.mozilla.org/show_bug.cgi?id=1314429 target going broadly with e10s to add-ons users], everyone except MPC=False or specifically excluded (due to issues found)
*Beta 51 is expanding [https://bugzilla.mozilla.org/show_bug.cgi?id=1314429 e10s to all users with add-ons unless they are specifically marked MPC=False] or specifically excluded (due to issues found)
**Looking to learn if "shims" impacts performance/stability significantly in Beta.
**Goal: See if "shims" impacts performance/stability significantly in Beta.
**The first 5 Betas will be a Baseline - using the same criteria as Release 50
**The first 5 Betas will be a Baseline - using the same criteria as Release 50
**The expanded addons-e10s experiment will be turned on in Beta 6 (~Dec 10)
**The expanded addons-e10s experiment will be turned on in Beta 6 (~Dec 10) until Jan 13th
**We need the Baseline to correlate issues to specific add-ons if needed, using direct profile comparison.
**We need the Baseline to correlate issues to specific add-ons if needed, using direct profile comparison.
**In 49 and 50 the qualification criteria limited the number of users activated at once.  Beta 51 targeting would be more users than we want to activate at once in Release.  If the Beta goes well, Release expansion criteria will be Release 50 requirements (MPC=True and webextensions) and a list of all add-ons that hit a threshold of use in Beta 51.
**In 49 and 50 the qualification criteria limited the number of users activated at once.  Beta 51 Release expansion would be more users than we want to activate at once.  If the Beta goes well, Release expansion criteria will be Release 50 requirements (MPC=True and webextensions) and a list of all add-ons that hit a threshold of use in Beta 51 (threshold TBD).
 
 


== Beta/Release 51 Details ==
== Beta/Release 51 Details ==
Confirmed users
1,094

edits