Successful experiment clean up of `trial_email_validation`
Summary
The experiment is currently rolled out to 100% of users and has been deemed a success. The changes need to become an official part of the product.
- Related feature flag rollout issue: https://gitlab.com/gitlab-org/gitlab/-/issues/368999#note_1123489774
- Related engineering issue: https://gitlab.com/gitlab-org/gitlab/-/issues/325525
Steps
-
Determine whether the feature should apply to SaaS and/or self-managed - SaaS only as the form validation only exists on the SaaS free signup experience
-
Determine whether the feature should apply to EE - and which tiers - and/or Core - EE as SaaS is a version of EE
-
Determine if tracking should be kept as is, removed, or modified. - Tracking should be kept in place
-
Ensure any relevant documentation has been updated.Doesn't apply -
Consider changes to any feature_category:
introduced by the experiment if ownership is changing (PM for Growth and PM for the new category as DRIs) -
Check to see if the experiment introduced new design assets. Add them to the appropriate repos and document them if needed. -
Optional: Migrate experiment to a default enabled feature flag for one milestone and add a changelog. Converting to a feature flag can be skipped at the ICs discretion if risk is deemed low with consideration to both SaaS and (if applicable) self managed - This is how the experiment was conducted. The feature flag has been set to enabled for at least one milestone now. Since 2022-09-12
-
In the next milestone, remove the feature flag if applicable -
After the flag removal is deployed, clean up the feature/experiment feature flags by running chatops command in #production
channel -
Ensure the corresponding Experiment Rollout issue is updated
Edited by Ross Byrne