Closed Bug 1499110 Opened 6 years ago Closed 6 years ago

Make CFR/ASR preferences compatible with roll-outs

Categories

(Firefox :: Messaging System, defect, P1)

63 Branch
defect

Tracking

()

VERIFIED FIXED
Firefox 65
Iteration:
65.2 - Nov 16
Tracking Status
firefox64 + verified
firefox65 + verified

People

(Reporter: tspurway, Assigned: k88hudson)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Let's make sure CFR is pref'd on for 64 Beta, but disabled for 64 Release
Blocks: 1471328
Iteration: 63.4 - Aug 20 → 64.3 (Oct 12)
Iteration: 64.3 (Oct 12) → 65.1 (Nov 2)
The plan is to assume we'll want CFR on in 64 including Beta and Release. And given that we're on 65 Nightly already, we'll just change the default to on in 65 and uplift to 64 (and no channel checks).

If the results from the study in 63 Release result in turning off, we'll then want to uplift to 64 turning off for Release.
Summary: Pref On CFR for 64 Beta → Pref On CFR for 64 and later
Iteration: 65.1 (Nov 2) → 65.2 (Nov 16)
Assignee: nobody → khudson
Priority: P2 → P1
Blocks: 1505929
https://hg.mozilla.org/mozilla-central/rev/9fce755a1262
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 65
The study on 63 release (bug 1496181) started November 12.  Running for 3 weeks means end around Dec 3, allowing some time for analysis puts us really really close to the 64 release date.  Is this something we could ship via a pref rollout if time runs out?
Sure, that sounds good to me.

I will uplift the necessary changes to make this possible
Summary: Pref On CFR for 64 and later → Make CFR preference compatible with roll-outs
Summary: Make CFR preference compatible with roll-outs → Make CFR/ASR preferences compatible with roll-outs
Depends on: 1505551
Comment on attachment 9026523 [details]
Bug 1499110 - Make CFR/ASR preferences compatible with roll-outs

[Beta/Release Uplift Approval Request]

Feature/Bug causing the regression: Bug 1499110

User impact if declined: We will not be able to roll-out Contextual Feature recommendations or Snippets to users in 64, which are critical to our goals to improve retention, collect appropriate data to make better decisions in the future. Rolling out reduces risks rather than turning everything on at once. (Note that Bug 1505551 must be landed before this one)

Is this code covered by automated tests?: No

Has the fix been verified in Nightly?: No

Needs manual test from QE?: Yes

If yes, steps to reproduce: Set up devtools using the "Prerequisites" instructions here: https://docs.google.com/document/d/1U8QegwAIXcm3pkznL0mvZ2r0tNXSsnbu9rH82c2dNyQ/edit#heading=h.v67ohgjjeblk
    Navigate to about:newtab#asrouter to check the status of all providers.
    Snippets and CFR providers should be ENABLED in a Nightly build, and DISABLED in a release/beta build.

List of other uplifts needed: Bug 1505551

Risk to taking this patch: Medium

Why is the change risky/not risky? (and alternatives if risky): Unfortunately it's difficult to add automated testing for default pref values in different channels, however,  this change is required by Normandy's architecture to enable roll-outs; having the ability to roll-back will be less risky than launching at once without that ability.

String changes made/needed:
Attachment #9026523 - Flags: approval-mozilla-beta?
Waiting on review to merge this to nightly.
Pushed by khudson@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c54f764614f7
Make CFR/ASR preferences compatible with roll-outs r=ursula
Comment on attachment 9026523 [details]
Bug 1499110 - Make CFR/ASR preferences compatible with roll-outs

allow AS CFR rollouts, approved for 64.0b12
Attachment #9026523 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Flags: qe-verify+
I have verified the fix on the latest Beta build 64.0b12 (Build ID 20181122182000) and on the latest Nightly 65.0a1 (Build ID 20181122220059) on Windows 10 x64, Mac 10.13.3, and Arch Linux 4.16.
Status: RESOLVED → VERIFIED
Flags: qe-verify+
Component: Activity Streams: Newtab → Messaging System
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: