Open jaredlockhart opened 2 years ago
This change will introduce the ability to target multiple features with a single experiment. To support this, we are adding a new key to the Branch
type called features
which will contain an array of objects each of which contains
featureId
: stringenabled
: boolvalue
: objectDeprecating the feature
key on Branch
will follow with a subsequent schema change.
Desktop/Experimenter Epic: https://mozilla-hub.atlassian.net/browse/EXP-1610
Mobile Epic: https://mozilla-hub.atlassian.net/browse/SDK-342
We have tested the Multifeature client side as part of our weekly Nimbus testing in week Nov 1 - Nov 5 for mobile and week Nov 8 - Nov 11 for desktop. We have found two issues:
We have performed additional testing. You can find the TestRail test runs here. We have found the following issue, which we understand was resolved after Bug 1738286 was implemented:
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] File tickets/epics in Nimbus Engineering to implement the changes in Experimenter and add them in a comment below, including:
[x] Comment below indicating which version of each client application includes the changes
[ ] File tickets/epics in Jetstream to adapt it to any incoming changes that affect its analysis
When Experimenter Changes Are Complete