the feature can be officially announced in a release blog post.
- [ ] `/chatops run auto_deploy status <merge-commit>`
-[ ] Close [the feature issue](ISSUE LINK) to indicate the feature will be released in the current milestone.
- [ ] (Optional) Close this issue and create a separate issue for scheduling the steps below to "Clean up the feature flag".
- [ ] (Optional) Close this issue and create a separate issue for scheduling the steps below to "Release the feature".
**WARNING:** This approach complicates [clean up](https://docs.gitlab.com/ee/development/feature_flags/controls.html#cleaning-up).
For example, on-premise users could disable the feature on their GitLab instance. But when you
...
...
@@ -118,7 +118,7 @@ remove the flag at some point, they suddenly see the feature as enabled and they
to the previous behavior. To avoid this potential breaking change, use this approach only for urgent
matters.
### Clean up the feature flag
### Release the feature
After the feature has been [deemed stable](https://about.gitlab.com/handbook/product-development-flow/feature-flag-lifecycle/#including-a-feature-behind-feature-flag-in-the-final-release),
the [clean up](https://docs.gitlab.com/ee/development/feature_flags/controls.html#cleaning-up)
