Closed Bug 1583262 Opened 4 months ago Closed 3 months ago

Messaging router custom code to support 71 first run experiments

Categories

(Firefox :: Messaging System, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
Firefox 71
Iteration:
71.3 - Sept 30 - Oct 13
Tracking Status
firefox70 --- unaffected
firefox71 --- fixed

People

(Reporter: pdahiya, Assigned: pdahiya)

References

(Blocks 1 open bug)

Details

(Keywords: github-merged)

Attachments

(1 file)

Update custom code to generate branches and manage enrollment for 71 about:welcome experiments

https://searchfox.org/mozilla-central/source/browser/components/newtab/lib/ASRouter.jsm#985

Assignee: nobody → pdahiya
Iteration: --- → 71.3 - Sept 30 - Oct 13
Priority: -- → P1
Duplicate of this bug: 1552285

NI Felix to help answer query here https://github.com/mozilla/activity-stream/pull/5330#discussion_r333740635, essentially confirming the change in messaging custom code that's going to split 100% of our users in 6 interrupt experiment branches in 71. Thanks!

Experiment bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1585820#c0

Technical plan attached to meta bug 1564149

Flags: needinfo?(flawrence)

I can't answer that comment from the information available from that bug, the experimenter page or the linked docs (though the PRD comes close). In order to answer that question, I need to understand the experiment design. It's possible that I was involved in this earlier but after a considerable hunt for evidence (looking for a meeting in the hope it would have notes!) I couldn't find anything.

I'm meeting with k88hudson tomorrow morning; hopefully we can talk about this then. I may also need to talk to jimt in order to resolve this issue - I'll reach out to him afterwards if necessary.

Flags: needinfo?(flawrence)

100% of the population of new users split evenly among the 6 branches is OK by me. Product and/or execs might be nervous about dedicating 100% of the population to untested experiences and I'm not speaking on behalf of them - as a DS I have no objections and this sounds reasonable to me. I still need to review in detail what the branches are and what the goals of the experiment are, and there may be changes required after I do that.

Attached file GitHub Pull Request
Blocks: 1589802
Status: NEW → RESOLVED
Closed: 3 months ago
Keywords: github-merged
Resolution: --- → FIXED
Target Milestone: --- → Firefox 71

(In reply to Felix Lawrence from comment #4)

I still need to review in detail what the branches are and what the goals of the experiment are, and there may be changes required after I do that.

I did that and left this comment on the technical plan. I pinged jimt about it on slack.

You need to log in before you can comment on or make changes to this bug.