ESR 38 is the last supported release of Firefox to make use of the mozpub-track-digest256 list. It is officially out of support on 2016-06-07 when ESR 45.2 is released. We should remove it from stage and prod. Once that's done, we can remove the logic for the exceptions from the list creation script and we can delete this repo: https://github.com/mozilla-services/shavar-list-exceptions We will also be able to remove "mozpub" (not "moztestpub" though) from the end-to-end tests.

Since we're already changing the list configs (bug 1258038), the end-to-end tests (bug 1258043) and the list creation script as part of the DNT loophole fix, it probably makes sense to do this cleanup in the same deployment / QA cycle.

Sounds like we can do this now? We should be able to make the shavar config change while we change the config to serve the separate DNT lists. :ckolos - Do you prefer to make shavar config changes like these together in a single deploy? Or do them separately to minimize and isolate changes?

each config change would require a full deploy/QA cycle, so batching them is the only thing that makes sense.

(In reply to Chris Kolosiwsky [:ckolos] from comment #3) > each config change would require a full deploy/QA cycle, so batching them is > the only thing that makes sense. agreed.

I'm going to roll this into the same PR that separates DNT-aware lists: https://github.com/mozilla-services/shavar-list-creation-config/pull/11 :ckolos - should I use the same branch? Since Jenkins is already configured to use the branch to create lists? And, can we schedule this merge + deploy for Tuesday or Wednesday before you go on PTO? :rpapa, :rbillings - are either of you able to run thru the QA test plan on Tuesday/Wednesday during a deploy? I seem to remember one of you is also on PTO this week?

Made the commit for this: https://github.com/mozilla-services/shavar-list-creation-config/compare/remove-mozpub-track-digest-1277446?expand=1 AFAICT, this is all we need to be able to test on stage.

(In reply to Luke Crouch [:groovecoder] from comment #5) > I'm going to roll this into the same PR that separates DNT-aware lists: > > https://github.com/mozilla-services/shavar-list-creation-config/pull/11 > > :ckolos - should I use the same branch? Since Jenkins is already configured > to use the branch to create lists? And, can we schedule this merge + deploy > for Tuesday or Wednesday before you go on PTO? > > :rpapa, :rbillings - are either of you able to run thru the QA test plan on > Tuesday/Wednesday during a deploy? I seem to remember one of you is also on > PTO this week? :groovecoder, thanks, Luke. :rbillings is on PTO til end-of-month and I'm going to be tied up w/ push loadtesting the better part of week & also on PTO Fri., Mon. I see on the calendar that :ckolos also has a short week, but if he does have time to do STAGE deploy, there's a chance I could re-start some of the testing. In terms of scheduling, I probably won't be able to start this in earnest til sometime next week.

Re: :ckolos - should I use the same branch? Since Jenkins is already configured to use the branch to create lists? And, can we schedule this merge + deploy for Tuesday or Wednesday before you go on PTO? Yup. Please do so.

This was done in the last production deploy.