Services/Shavar/Lists: Difference between revisions
Jump to navigation
Jump to search
Rpappalardo (talk | contribs) (Adding server release info) |
Rpappalardo (talk | contribs) m (summary update) |
||
| Line 3: | Line 3: | ||
== Summary == | == Summary == | ||
The purpose of this wiki is to provide: | The purpose of this wiki is to provide information related to the Shavar server lists: | ||
* A list-centric matrix of shavar dependencies | * A list-centric matrix of shavar dependencies | ||
** | ** Can be used to easily view a match-up between lists and (a) when they will be available from the shavar server as well as (b) when they will enabled in a specific version of the Firefox client | ||
* A Basic overview of list "pref sets" used for testing | * A Basic overview of list "pref sets" used for testing | ||
* A Summary of the various list repositories and what they're used for | |||
'''Client-side''' | '''Client-side''' | ||
| Line 18: | Line 19: | ||
[[#top]] | [[#top]] | ||
== List Dependency Matrix == | == List Dependency Matrix == | ||
| Line 215: | Line 217: | ||
|} | |} | ||
[[#top]] | |||
= List Testing - "Pref Sets" = | |||
For testing shavar and tracking protection client behavior (in the browser), we need to set certain custom preferences in about:config. | |||
Below you will find a matrix of test "pref sets" and their usage | |||
{| class="wikitable" | |||
|- | |||
! Pref Set | |||
! Key Feature | |||
! Comments | |||
|- | |||
| mozstd | |||
| determine what list client uses to block things | |||
| | |||
|- | |||
| mozfull | |||
| tracking table pref - we switch the blacklist, keep same whitelist | |||
| | |||
|- | |||
| mozstaging | |||
| for staging changes to the disconnect list | |||
| | |||
|- | |||
| moztestpub | |||
| change white & blacklist because we those are the ones we can edit in github | |||
| should be called "editing-list" or "e2e-test". For all other tests, the actual underlying list is the disconnect one (except mozstaging which has another upstream repo) | |||
|} | |||
[[#top]] | |||
= List Types = | |||
# staging one | |||
# disconnect list | |||
# editing list | |||
[[#top]] | [[#top]] | ||
Revision as of 01:49, 1 July 2016
Shavar Lists
Summary
The purpose of this wiki is to provide information related to the Shavar server lists:
- A list-centric matrix of shavar dependencies
- Can be used to easily view a match-up between lists and (a) when they will be available from the shavar server as well as (b) when they will enabled in a specific version of the Firefox client
- A Basic overview of list "pref sets" used for testing
- A Summary of the various list repositories and what they're used for
Client-side
- What lists are currently being consumed by the client (in Nightly, DevEd, Beta, etc.)?
- What lists will be removed / added and when (and in what client version)
Server-side
- What lists are currently being server in STAGE, in PRODUCTION?
- What lists are to be removed (no longer served) and with what deployment?
- What lists are to be added (to be served) and with what deployment?
List Dependency Matrix
| List Name | Shavar Server Deploy | Firefox Client Release | Purpose | Comments
(Ops/QA/Dev) | ||||
|---|---|---|---|---|---|---|---|---|
| STG | PRD | Add
in |
Remove
in |
Add
in |
Remove
in | |||
| mozfull-track-digest256 | X | X | 43 | diary testing list | ||||
| mozfullstaging-track-digest256 | X | X | 0.7 | diary testing list | Never shipped w/ FF | |||
| mozplugin-block-digest256 | X | X | 0.7 | 47 | ||||
| mozplugin2-block-digest256 | X | X | 0.7 | 47 | ||||
| mozpub-track-digest256 | X | X | 0.7 | 38 | 42 | |||
| mozstd-track-digest256 | X | X | 42 | |||||
| mozstd-trackwhite-digest256 | X | X | 42 | |||||
| mozstdstaging-track-digest256 | X | X | 0.7 | testing new entries before we
submit them to Disconnect |
Never shipped w/ FF | |||
| mozstdstaging-trackwhite-digest256 | X | X | 0.7 | testing new entries before we
submit them to Disconnect |
Never shipped w/ FF | |||
| moztestpub-track-digest256 | X | testing additions and removals during
the end-to-end tests |
Never shipped w/ FF | |||||
| moztestpub-trackwhite-digest256 | X | testing additions and removals during
the end-to-end tests |
Never shipped w/ FF | |||||
| base-track-digest256 | X | X | ||||||
| basew3c-track-digest256 | X | X | ||||||
| baseeff-track-digest256 | X | X | ||||||
| content-track-digest256 | X | X | ||||||
| contentw3c-track-digest256 | X | X | ||||||
| contenteff-track-digest256 | X | X | ||||||
List Testing - "Pref Sets"
For testing shavar and tracking protection client behavior (in the browser), we need to set certain custom preferences in about:config.
Below you will find a matrix of test "pref sets" and their usage
| Pref Set | Key Feature | Comments |
|---|---|---|
| mozstd | determine what list client uses to block things | |
| mozfull | tracking table pref - we switch the blacklist, keep same whitelist | |
| mozstaging | for staging changes to the disconnect list | |
| moztestpub | change white & blacklist because we those are the ones we can edit in github | should be called "editing-list" or "e2e-test". For all other tests, the actual underlying list is the disconnect one (except mozstaging which has another upstream repo) |
List Types
- staging one
- disconnect list
- editing list
List Testing - "Pref Sets"
For testing shavar and tracking protection client behavior (in the browser), we need to set certain custom preferences in about:config.
Below you will find a matrix of test "pref sets" and their usage
| Pref Set | Key Feature | Comments |
|---|---|---|
| mozstd | determine what list client uses to block things | |
| mozfull | tracking table pref - we switch the blacklist, keep same whitelist | |
| mozstaging | for staging changes to the disconnect list | |
| moztestpub | change white & blacklist because we those are the ones we can edit in github | should be called "editing-list" or "e2e-test". For all other tests, the actual underlying list is the disconnect one (except mozstaging which has another upstream repo) |
List Types
- staging one
- disconnect list
- editing list