Closed Bug 1603071 Opened 11 months ago Closed 10 months ago

Enable release snippets in Nightly without telemetry


(Firefox :: Messaging System, enhancement, P1)




Firefox 73
73.2 - Dec 16 - Jan 5
Tracking Status
firefox73 --- verified


(Reporter: andreio, Assigned: andreio)


(Blocks 1 open bug)



(1 file)

Currently in the nightly release channel has few or no snippets at all while release has 100s.
Performance regressions can go unnoticed and our recent (bug 1600335) histogram will not capture any spikes.
Plan is to add a pref (possibly nightly only) that changes the endpoint to release while at the same time disables telemetry. We don't want to affect the campaign numbers and also if required (if we decide to ship a campaign on Nightly) we can switch back easily.

Assignee: nobody → andrei.br92
Type: defect → enhancement
Iteration: --- → 73.2 - Dec 16 - Jan 5
Priority: -- → P1
Pushed by
Enable release snippets in Nightly without telemetry r=k88hudson

After talking with the Snippets team, there seem to be plan to run again Nightly snippets in the near future. Andrei, I think we discussed about the possibility to merge Release and Nightly snippets on the fly in browser. Is this possible? If so, this satisfies both Snippets team that gets to run Nightly Snippets (along with Release in Nightly channel) and your team that gets Release Snippets in Nightly channel.

lmk what you think. Thanks!

Also in the case above, what happens with telemetry? If it's super simple to report only on Nightly Snippets that would be great, otherwise we need to discuss options.

Closed: 10 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 73

I have verified this issue on Firefox Nightly 73.0a1 (Build ID: 20191219095006) on Windows 10 x64, Mac 10.14.6 and Ubuntu 18.04.2.
I can confirm the following:

  • browser.newtabpage.activity-stream.asrouter.useReleaseSnippets preference is set on true by default
  • the Snippets are displayed on profiles older than 30 days
  • the telemetry pings are not displayed in the browser console.
You need to log in before you can comment on or make changes to this bug.