Closed Bug 1630682 Opened 5 years ago Closed 4 years ago

[Experiment] Staged Rollout: Blocklist v3 (Beta rollout) Fx 78.0 to 78.0 Beta

Categories

(Shield :: Shield Study, task, P3)

Tracking

(firefox78+ disabled)

RESOLVED FIXED
Tracking Status
firefox78 + disabled

People

(Reporter: experimenter, Assigned: jorgev)

References

()

Details

(Whiteboard: [no-nag])

Blocklist v3

New version of blocklist, etc

Experimenter is the source of truth for details and delivery. Changes to Bugzilla are not reflected in Experimenter and will not change delivery configuration.

Data Science Issue:
More information: https://experimenter.services.mozilla.com/experiments/blocklist-v3/

Summary: [Experiment]: Staged Rollout: Blocklist v3 → [Experiment] Staged Rollout: Blocklist v3 (Beta rollout) Fx 78.0 to 78.0 Beta
Start Date: 2020-06-10 End Date: 2020-09-18
Assignee: nobody → jorge
Whiteboard: [no-nag]

Jorge, according to https://experimenter.services.mozilla.com/experiments/blocklist-v3/ this was supposed to start at 25% on June 10, bump to 75% on June 17 and 100% on July 1, but https://normandy.cdn.mozilla.net/api/v3/recipe/987/ says we're still at 25%. In the meantime beta 79 started, and the rollout only targets beta 78, so we're actually rolling back as people upgrade. Is that intentional?

Flags: needinfo?(jorge)

Yes, we didn't go past 25% on beta due to a process error with the rollout. We thought it would move to 75% and 100% automatically, but that didn't happen. We have bug 1631018, which will turn on the pref permanently on Nightly, Beta, and eventually ESR, but we're currently investigating an issue we need to address before.

Now we have a release rollout we're setting up (https://experimenter.services.mozilla.com/experiments/blocklist-v3-release-rollout/), which should start soon if we solve the issue that came up on bug 1631018.

Flags: needinfo?(jorge)
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.