1201741 - Rename the mozpub2-track-digest256 list

Status: RESOLVED FIXED

(Cloud Services :: Server: Shavar, defect)

Description

[François Marier [:francois]]

The name "mozpub2-track-digest256" was meant to be a temporary name to enable the diary study (bug 1198904).

Before we land support for multiple lists in 43 (bug 1177085), we should rename that list to something more descriptive.

I suggested mozfull-track-digest256.

Comment 1

[François Marier [:francois]]

Of course, we should do this after the diary study is over because they're using mozpub2-track-digest256 in these builds.

Comment 2

[François Marier [:francois]]

The diary study will go likely through 9/18 according to Javaun.

Given that timeframe and the beta merge on the 21st, perhaps what we need to do is to temporary duplicate the lists we want to rename and offer them under different names to all clients.

So in the case of mozpub2-track-digest256, what I'm proposing is this:

1. [now] start generating "mozfull-track-digest256" (the same as mozpub2) and serving it on stage
2. [before Sep 21] go to prod with mozfull-track-digest256 but not mozpub2-track-digest256
3. [after Sep 18] stop generating mozpub2 on stage

Chris, Ryan, does that seem reasonable to you?

Note: The mozpub2 list has never hit Nightly (and never will). It's only in custom builds for the diary study.

Comment 3

[Chris Kolosiwsky [:ckolos] (ckolos has left the building)]

This is done in stage. Pending e2e testing of the current stage stack, this will be available in prod with the 0.6.5.2 deploy.

Comment 4

[François Marier [:francois]]

This is done in production too.