[Feature flag] Cleanup `fetch_commits_for_bitbucket_server`
Summary
This issue is to cleanup the fetch_commits_for_bitbucket_server
feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.
Owners
- Team: NAME_OF_TEAM
- Most appropriate slack channel to reach out to:
#g_TEAM_NAME
- Best individual to reach out to: NAME
- PM: NAME
Stakeholders
Expectations
What might happen if this goes wrong?
Cleaning up the feature flag
-
Specify in the issue description if this feature will be removed completely or will be productized as part of the Feature Flag cleanup -
Create a merge request to remove fetch_commits_for_bitbucket_server
feature flag. Ask for review and merge it.-
Remove all references to the feature flag from the codebase. -
Remove the YAML definitions for the feature from the repository. -
Create a changelog entry.
-
-
Ensure that the cleanup MR has been deployed to both production and canary. If the merge request was deployed before the code cutoff, the feature can be officially announced in a release blog post. -
/chatops run auto_deploy status <merge-commit-of-cleanup-mr>
-
-
Close the feature issue to indicate the feature will be released in the current milestone. -
If not already done, clean up the feature flag from all environments by running these chatops command in #production
channel:/chatops run feature delete fetch_commits_for_bitbucket_server --dev --pre --staging --staging-ref --production
-
Close this rollout issue.
Edited by Vasilii Iakliushin