Experiment Cleanup: highlight_paid_features_during_active_trial
highlight_paid_features_during_active_trial - Code removal & cleanup
Summary
Per team discussion and agreement, we've decided to remove the experiment code for the highlight_paid_features_during_active_trial experiment.
[ ] Determine if issues in &6012 (closed) are necessary to complete experiment cleanup
Steps
-
Determine whether the feature should apply to SaaS and/or self-managed -
Determine whether the feature should apply to EE - and which tiers - and/or Core -
Determine if tracking should be kept as is, removed, or modified. -
Ensure any relevant documentation has been updated. -
Determine whether there are other concerns that need to be considered before removing the feature flag. - These are typically captured in the
Experiment Successful Cleanup Concerns
section of the rollout issue.
- These are typically captured in the
-
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 -
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 Doug Stull