diff options
| author | Ævar Arnfjörð Bjarmason <avarab@gmail.com> | 2021-01-13 14:27:44 +0300 |
|---|---|---|
| committer | Ævar Arnfjörð Bjarmason <avarab@gmail.com> | 2021-01-18 19:50:49 +0300 |
| commit | 26a082cfbf359af14593a5deb3dfd78f17ff1bd8 (patch) | |
| tree | 1debfb64dcfadf6da7e625e83c690282f3fba9c3 /doc | |
| parent | 86c8480e89b290af7d30dd5d5d09a53df8b107a8 (diff) | |
Feature flag rollout doc: clarify the "Feature flag labels" item
I added this because of a question @pks-t had in
https://gitlab.com/gitlab-org/gitaly/-/merge_requests/2995#note_484390302
It's easy to miss that we auto-add the featureflag::disabled flag
initially, let's cover that and provide handy links to the tracker to
see the status of each label.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/PROCESS.md | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/PROCESS.md b/doc/PROCESS.md index 171bac470..d3439f2d6 100644 --- a/doc/PROCESS.md +++ b/doc/PROCESS.md @@ -61,6 +61,20 @@ The rest of this section is help for the individual checklist steps in time doing this you might want to first skip ahead to the help below, you'll likely need to file some access requests. +#### Feature flag labels + +The lifecycle of feature flags is monitored via issue labels. + +When the issue is created from a template it'll be created with +[`featureflag::disabled`][featureflag-disabled]. Then as part of the +checklist the person rolling it out will add +[`featureflag::staging`][featureflag-staging] and +[`featureflag::production`][featureflag-production] flags to it. + +[featureflag-disabled]: https://gitlab.com/gitlab-org/gitaly/-/issues?label_name[]=featureflag%3A%3Adisabled +[featureflag-staging]: https://gitlab.com/gitlab-org/gitaly/-/issues?label_name[]=featureflag%3A%3Astaging +[featureflag-production]: https://gitlab.com/gitlab-org/gitaly/-/issues?label_name[]=featureflag%3A%3Aproduction + #### Is the required code deployed? A quick way to see if your MR is deployed is to check if [the release |