Closed Bug 1579256 Opened 5 years ago Closed 4 years ago

Launch first run experiments using FirstStartup service

Categories

(Firefox :: Messaging System, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
Iteration:
74.1 - Jan 6 - Jan 19
Tracking Status
firefox70 --- unaffected
firefox71 --- wontfix
firefox72 --- affected

People

(Reporter: pdahiya, Assigned: pdahiya)

References

Details

With https://bugzilla.mozilla.org/show_bug.cgi?id=1576507 fixed, refactor code to use FirstStartUp service to launch first run experiments.

Summary: Launch about:welcome experiments using FirstStartup service → Launch first run experiments using FirstStartup service
Iteration: --- → 71.1 - Sept 2 - 15
Priority: -- → P1

StartupService is setup to run on windows only. With switch to use StartupService, we will be restricting enrollment and first run experiment to windows users. NI Jim to verify with data science if we are good to go ahead with the switch. Thanks

Flags: needinfo?(jimthomas)
Iteration: 71.1 - Sept 2 - 15 → 71.2 - Sept 16 - 29
Assignee: nobody → tspurway

The plan is to wait on using StartupService until we can test out the integration more. For this experiment in particular we'll still use our existing, in-client framework, which is not windows-only.

Flags: needinfo?(jimthomas)
Iteration: 71.2 - Sept 16 - 29 → 71.3 - Sept 30 - Oct 13
Assignee: tspurway → nobody
Iteration: 71.3 - Sept 30 - Oct 13 → 72.1 - Oct 21 - Nov 3
Iteration: 72.1 - Oct 21 - Nov 3 → 72.2 - Nov 4 - 17
Iteration: 72.2 - Nov 4 - 17 → 72.3 - Nov 18 - Dec 1
Assignee: nobody → pdahiya
Iteration: 72.3 - Nov 18 - Dec 1 → 73.1 - Dec 2 - Dec 15

Scope of this bug is to track launching dynamic triplets first run experiment in beta via Normandy using FirstStartup Service. NI Ron to help link experiment ticket to this bug. Thanks

Flags: needinfo?(rmanning)
Flags: needinfo?(rmanning)
Iteration: 73.1 - Dec 2 - Dec 15 → 73.2 - Dec 16 - Jan 5
Iteration: 73.2 - Dec 16 - Jan 5 → 74.1 - Jan 6 - Jan 19
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.