Closed Bug 1312779 Opened 4 years ago Closed 4 years ago
Continue the Beta 50 add-ons e10s targeting criteria into 50 release
Despite not having the 2 uplifts - we want to continue the experiment into 50 release. This is based on the metrics we saw from Beta being good. We are looking now to see if there are other measurements we should be looking at for start up time - but do not see a reason not to continue to release with the beta targets. specific add-ons can be disabled if they cause problems - though Felipe noted that only 55% of users get over the air system updates. so this is all MPC=true, all webextensions, the few specified in bug (for test pilot, etc) that are neither MPC=true or webextensions, & blocking tab-mix-plus (which is MPC=true but has issues still)
Assignee: nobody → felipc
Status: NEW → ASSIGNED
Comment on attachment 8805594 [details] Bug 1312779 - Enable e10s with all mpc=true addons. https://reviewboard.mozilla.org/r/89350/#review88582 \o/
Attachment #8805594 - Flags: review?(mconley) → review+
Comment on attachment 8805594 [details] Bug 1312779 - Enable e10s with all mpc=true addons. https://reviewboard.mozilla.org/r/89350/#review88584 Oh - don't forget to bump the install.rdf version!
(In reply to Mike Conley (:mconley) - (digging out of review / needinfo backlog) from comment #3) > Comment on attachment 8805594 [details] > Bug 1312779 - Enable e10s with all mpc=true addons. > > https://reviewboard.mozilla.org/r/89350/#review88584 > > Oh - don't forget to bump the install.rdf version! * sigh * every time!
Comment on attachment 8805594 [details] Bug 1312779 - Enable e10s with all mpc=true addons. Approval Request Comment [Feature/regressing bug #]: Configure firefox release to use the same e10s-addons policy as what was tested during beta. [User impact if declined]: Firefox 50 will continue to use the same list of whitelisted add-ons for e10s as Firefox 49. The current goal is to enable all add-ons which have explicitly marked themselves as multiprocessCompatible, which will bump the number of e10s-addons users from 3% to 6% on release. [Describe test coverage new/current, TreeHerder]: Tested during the entire beta cycle on the beta channel [Risks and why]: The risk inherent from allowing more add-ons to run with e10s [String/UUID change made/needed]: none
Heads up that it looks like this didn't autoland properly.
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/f069d69f1a18 Enable e10s with all mpc=true addons. r=mconley
Thanks for the heads up, Mike. This was due to a merge conflict with bug 1301131, which had been backed out from beta (where I wrote my patch), but not on central/aurora. I backed it out from everything to facilitate merging this one tomorrow.
Comment on attachment 8805594 [details] Bug 1312779 - Enable e10s with all mpc=true addons. e10s enablement for mpc addons on 50 release, this should be in the first rc build
You need to log in before you can comment on or make changes to this bug.