Commit c92f0085 authored by Marin Jankovski's avatar Marin Jankovski

Merge branch 'jarv/adds-note-about-ff-coverage' into 'master'

Adds a note that we require coverage for feature flag modifications

See merge request gitlab-org/gitlab!61022
parents e602dd42 0fcfcd44
...@@ -75,7 +75,10 @@ Are there any other stages or teams involved that need to be kept in the loop? ...@@ -75,7 +75,10 @@ Are there any other stages or teams involved that need to be kept in the loop?
issue](https://about.gitlab.com/handbook/engineering/infrastructure/change-management/#feature-flags-and-the-change-management-process). Cross issue](https://about.gitlab.com/handbook/engineering/infrastructure/change-management/#feature-flags-and-the-change-management-process). Cross
link the issue here if it does. link the issue here if it does.
- [ ] Ensure that you or a representative in development can be available for at least 2 hours after feature flag updates in production. If a different developer will be covering, or an exception is needed, please inform the oncall SRE by using the `@sre-oncall` Slack alias.
*Partial Rollout Phase* *Partial Rollout Phase*
- [ ] Enable on GitLab.com for individual groups/projects listed above and verify behaviour (`/chatops run feature set --project=gitlab-org/gitlab feature_name true`) - [ ] Enable on GitLab.com for individual groups/projects listed above and verify behaviour (`/chatops run feature set --project=gitlab-org/gitlab feature_name true`)
- [ ] Verify behaviour (See Beta Groups) and add details with screenshots as a comment on this issue - [ ] Verify behaviour (See Beta Groups) and add details with screenshots as a comment on this issue
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment