amateurvur.blogg.se - march 2023

SDK Performance fixes were excepted late into Beta 50 cycle - delaying 50 Release to Nov 15, 2016.Release stability metrics continue to have no significant difference between stability for e10s without add-ons and e10s with add-ons.

We need the Baseline to correlate issues to specific add-ons if needed, using direct profile comparison.

The expanded addons-e10s experiment will be turned on in Beta 6 (~Dec 10) until Jan 13th.

The first 5 Betas will be a Baseline - using the same criteria as Release 50.

Beta Goal: See if "shims" impacts performance/stability significantly in Beta.

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 51 Release expansion would be more users than we want to activate at once.

In 49 and 50 the qualification criteria limited the number of users activated at once.

Beta 51 expanded e10s to all users with add-ons unless they are specifically marked MPC=False or specifically excluded (due to issues found).

These are in addition Release 50 criteria of MPC=True and webextensions. These add-ons were in Beta and did not cause issues with Firefox performance or stability (functionality could not be tested, but if reported the add-ons were removed from sample).

Release 51 expanded to several hundred add-ons that were not marked (either MPC=True or MPC=False).

Ensuring that the targeting add-on accurately keeps e10s from users with add-ons marked MPC=False

The goal in 53 is to allow e10s to expand to all users, unless they have add-ons marked specifically MPC=False (not multiprocess compatible).

7.2 Improve Add-ons Discovery and ManagementĪdd-ons/e10s Program Status Report Exec Summary/Hot Topics - Feb 14th.

6 Current Program/Project Work - August 9th, 2016.

4 Add-on Developer Experience Status Report.

3.1 Exec Summary/Hot Topics - Aug 8th, 2016.2.1 Exec Summary/Hot Topics - Nov 30, 2016.