-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[fingerprint] - Onboard to Azure ExP #1260
Comments
@savannahostrowski I think when we last spoke, you mentioned that this is something we need to do in |
No, I think we'll still want to onboard to the experimentation platform long term. I'm thinking that it'd be beneficial when we ship fingerprinting and potentially want to iterate on the implementation/heuristics etc. |
@ellismg anything pending here? can we close? |
Allow experimentation rollouts to control the default alpha feature enablement. - If a feature flag for `alpha_<featureId>` is set to true, the alpha feature is enabled by default. User config takes precedence over the default. Also, moving the experimentation initialization to later in app initialization so that initialization only occurs when a command is fully parsed. Error commands should not trigger the flow. Partially addresses #1260
@weikanglim @ellismg did we configure the bits for the controlled rollout yet? Or just the client onboarding? |
@savannahostrowski Controlled rollout is done with #2703. Closing |
We will want to investigate how we can onboard to ExP so that we can A/B test features and conduct controlled rollouts.
The text was updated successfully, but these errors were encountered: