Closed brennie closed 1 year ago
The intent is to add an additional field for experiments, validationOptOut
, that, when true
, would prevent desktop from performing schema validation for the experiment. This is intended for cases where an experiment needs to launch but is failing validation due to schema errors or problems in the validation logic and the fixes for those issues cannot ride the trains in time.
This landed in Firefox desktop 107.
Welcome Change Captain! ⛵️
When making schema changes, follow this guidance to avoid breaking changes:
Rather than modifying an existing field, consider adding a new field with a new name and later deprecating the old field when it is no longer used
When deprecating an existing field, consider making it optional/nullable rather than removing it altogether and then removing it entirely when all clients/active experiments no longer depend on it
Proposing Schema Changes
When Client Changes Are Complete
When Client QA is Complete
When Bugs Are Resolved and Clients Are Released
[x] Comment below indicating which version of each client application includes the changes
[x] File tickets/epics in Nimbus Engineering to implement the changes in Experimenter and add them in a comment below, including:
[ ] File tickets/epics in Jetstream to adapt it to any incoming changes that affect its analysis
When Experimenter Changes Are Complete