Changes to e10srollout for Release 55

RESOLVED FIXED in Firefox 55

Status

()

enhancement
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: mrbkap, Assigned: mrbkap)

Tracking

54 Branch
Firefox 56
Points:
---

Firefox Tracking Flags

(firefox55 fixed, firefox56 fixed)

Details

Attachments

(1 attachment)

We're rolling out to Release 55 as follows:
  * 100% e10s vs. non-e10s (for eligible users).
  * 50%/50% 1 content process vs. 4 content processes.
  * Users with WebExtensions are *eligible* for multi.
  * Users with any other kind of add-on (mpc=true or not) are *not* eligible for multi.
Comment on attachment 8890929 [details]
Bug 1384985 - Update e10srollout for 55 to move to Release.

https://reviewboard.mozilla.org/r/162136/#review167410
Attachment #8890929 - Flags: review?(felipc) → review+
Pushed by mrbkap@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5b08a1e39e2a
Update e10srollout for 55 to move to Release. r=Felipe
Comment on attachment 8890929 [details]
Bug 1384985 - Update e10srollout for 55 to move to Release.

Approval Request Comment
[Feature/Bug causing the regression]: e10s-multi
[User impact if declined]: Fewer people on Release 55 will have e10s-multi
[Is this code covered by automated tests?]: No.
[Has the fix been verified in Nightly?]: n/a
[Needs manual test from QE? If yes, steps to reproduce]: Yes, SoftVision is aware.
[List of other uplifts needed for the feature/fix]: n/a
[Is the change risky?]: No.
[Why is the change risky/not risky?]: Our data shows that it's looking good.
[String changes made/needed]: n/a
Attachment #8890929 - Flags: approval-mozilla-beta?
https://hg.mozilla.org/mozilla-central/rev/5b08a1e39e2a
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 56
Comment on attachment 8890929 [details]
Bug 1384985 - Update e10srollout for 55 to move to Release.

e10srollout update for 55 release, should be in 55.0rc1
Attachment #8890929 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
You need to log in before you can comment on or make changes to this bug.