Closed
Bug 1714112
Opened 5 years ago
Closed 5 years ago
Add a new Fission pref or a new fission.experiment.enrollmentStatus pref value for Fission's Release channel staged rollout
Categories
(Core :: DOM: Content Processes, task, P2)
Core
DOM: Content Processes
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox91 | --- | fixed |
People
(Reporter: cpeterson, Assigned: kmag)
References
Details
Attachments
(1 file)
We use the fission.experiment.enrollmentStatus pref to enroll users into our Fission experiment. When we switched Nightly from an experiment to a staged rollout that set the fission.autostart pref directly, we ran into some problems with setting prefs and Normandy timing.
We want to avoid those issues when we switch our future Release experiment (M8) to a staged rollout (MVP). We need to determine whether we should add a new Fission rollout pref or a new fission.experiment.enrollmentStatus pref value for the staged rollout
Updated•5 years ago
|
Assignee: nobody → kmaglione+bmo
Status: NEW → ASSIGNED
Priority: P1 → P2
| Assignee | ||
Comment 1•5 years ago
|
||
This should be less confusing to users, and makes it easier to triage
about:support data.
Pushed by maglione.k@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/d7c690b2b06c
Add new Fission decision value for phased rollout enablement. r=nika,fluent-reviewers,flod
Comment 3•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox91:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•