diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-14 03:08:14 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-14 03:08:14 +0300 |
| commit | 427c549b6396885fb60a687326b6cd62878e4ca3 (patch) | |
| tree | 145713e2f6fdaf7499b0cb44010503e16b6248b9 /doc/development | |
| parent | 74a89b1221eaf780374bd1d4c5b2ee4a0f488908 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development')
| -rw-r--r-- | doc/development/feature_flags/process.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/development/feature_flags/process.md b/doc/development/feature_flags/process.md index c64b14a05a4..4b44c8dadca 100644 --- a/doc/development/feature_flags/process.md +++ b/doc/development/feature_flags/process.md @@ -15,7 +15,9 @@ should be leveraged: - Feature flags should remain in the codebase for as short period as possible to reduce the need for feature flag accounting. - The person operating with feature flags is responsible for clearly communicating - the status of a feature behind the feature flag with responsible stakeholders. + the status of a feature behind the feature flag with responsible stakeholders. The + issue description should be updated with the feature flag name and whether it is + defaulted on or off as soon it is evident that a feature flag is needed. - Merge requests that make changes hidden behind a feature flag, or remove an existing feature flag because a feature is deemed stable must have the ~"feature flag" label assigned. |