Closed Bug 1619770 Opened 5 years ago Closed 5 years ago

[Experiment] Pref-Flip Experiment: DoH TRR Selection ("Racing") Experiment Fx 74.0 to 74.0 Release

Categories

(Shield :: Shield Study, task, P3)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: experimenter, Assigned: nhi)

References

()

Details

User Story

Delivery Type: Pref Flip Experiment

    What is the preference we will be changing

doh-rollout.trrRace.enabled

    What are the branches of the experiment and what values should
    each branch be set to?

- Control measurement 100%:

Value: true

Measurement branch
        

    What version and channel do you intend to ship to?

0.75% of Release Firefox 74.0 to 74.0

    Are there specific criteria for participants?

Prefs:

Experiments:

Any additional filters:
avoid: https://experimenter.services.mozilla.com/experiments/doh-us-engagement-study-v4/
and https://experimenter.services.mozilla.com/experiments/doh-us-staged-rollout-to-all-us-desktop-users/
Countries: United States of America (US) 

Locales: all

    What is your intended go live date and how long will the experiment run?

Mar 10, 2020 - Mar 24, 2020 (14 days)

    What is the main effect you are looking for and what data will you use to
    make these decisions?

What is the main effect you are looking for and what data will
you use to make these decisions? What metrics are you using to measure success

Do you plan on surveying users at the end of the delivery? Yes/No.
Strategy and Insights can help create surveys if needed

    Who is the owner of the data analysis for this experiment?

tismith@mozilla.com

    Will this experiment require uplift?

True

    QA Status of your code:

This experiment was signed off as GREEN. For further information see:
https://experimenter.services.mozilla.com/experiments/doh-trr-selection-racing-experiment/#comment688
https://experimenter.services.mozilla.com/experiments/doh-trr-selection-racing-experiment/#comment694

    Link to more information about this experiment:

https://experimenter.services.mozilla.com/experiments/doh-trr-selection-racing-experiment/

DoH TRR Selection ("Racing") Experiment

We would like to support multiple default TRRs per region to reduce the real and perceived threat of DNS centralization. To do so we must use some selection criteria that does not reduce a user's privacy. Choosing the fastest provider is one such mechanism, but it will not reduce centralization if one provider always wins. This experiment will explore the distribution of performance of multiple TRRs as observed by Firefox users.

Experimenter is the source of truth for details and delivery. Changes to Bugzilla are not reflected in Experimenter and will not change delivery configuration.

More information: https://experimenter.services.mozilla.com/experiments/doh-trr-selection-racing-experiment/

Multiple default TRR racing

Firefox RC 74.0

We have finished testing the Multiple default TRR racing experiment for Firefox 74.

Quality status: GREEN - SHIP IT

Why is this feature green?

  • During testing, we haven’t found any issues.

Testing Summary:

Tested Platforms:

  • Windows 10 x64

  • macOS 10.15.1

  • Ubuntu 18.04 x64

Tested Firefox versions:

  • Firefox RC 74.0 en-US

Regards,
Robert Martin

Multiple default TRR racing

Firefox RC 74.0

We have finished testing the Multiple default TRR racing experiment for Firefox 74.

Quality status: GREEN - SHIP IT

Why is this experiment green?

  • We haven’t found any issues on any of the locales during testing.

Testing Summary:

Tested Platforms:

  • Windows 10 x64

  • macOS 10.15.1

  • Ubuntu 18.04 x64

Tested Firefox versions:

  • Firefox RC 74.0 en-CA

  • Firefox RC 74.0 de

  • Firefox RC 74.0 es-ES

Regards,

Robert Martin

User Story: (updated)
Summary: [Experiment]: Pref-Flip Experiment: DoH TRR Selection ("Racing") Experiment → [Experiment] Pref-Flip Experiment: DoH TRR Selection ("Racing") Experiment Fx 74.0 to 74.0 Release
User Story: (updated)
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.