1061871 - Point pre-release tiles server to development servers

Status: RESOLVED WONTFIX

(Firefox :: New Tab Page, defect)

Description

[Ed Lee :Mardak]

Bug 1058935 switched the prefs to tiles.services.mozilla.com from tiles.up.mozillalabs.com in preparation for Beta 33.

We want to be able to continue server development with actual users except deploying in-development changes to production is inefficient.

clarkbw says there should be a build-time config/flag to keep things from Release, so if we used that, we would be getting Beta/Aurora/Nightly traffic. There might be other flags for automatically turning off functionality earlier.

oyiptong/tspurway, how much traffic do we want / can we handle? Should we only take on requests from Nightly users? This also means if Nightly has some new functionality, e.g., using v3 endpoints, we'll need to get those deployed to production before mozilla-central code merges to mozilla-aurora. (As opposed pointing at development servers for both Nightly and Aurora giving us 6 more weeks before making sure the code needs to be deployed to production.)

Comment 1

[Lawrence Mandel [:lmandel] (use needinfo)]

(In reply to Ed Lee :Mardak from comment #0)
> clarkbw says there should be a build-time config/flag to keep things from
> Release, so if we used that, we would be getting Beta/Aurora/Nightly
> traffic. There might be other flags for automatically turning off
> functionality earlier.

The flag is EARLY_BETA_OR_EARLIER. This is set to 1 early in release and will be unset typically after beta4.

Comment 2

[Jessilyn Davis]

Hello!

This bug has been closed due to inactivity and/or the potential for this bug to no longer be an issue with the new Discovery Stream-powered New Tab experience.

Please help us triage by reopening if this issue still persists and should be addressed.

Thanks!