diff options
Diffstat (limited to 'doc/administration/feature_flags.md')
| -rw-r--r-- | doc/administration/feature_flags.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/administration/feature_flags.md b/doc/administration/feature_flags.md index 2a5260a1342..272009c1f3a 100644 --- a/doc/administration/feature_flags.md +++ b/doc/administration/feature_flags.md @@ -13,12 +13,12 @@ to deploy features in an early stage of development so that they can be incrementally rolled out. Before making them permanently available, features can be deployed behind -flags for a [number of reasons](../development/feature_flags/process.md#when-to-use-feature-flags), such as: +flags for a [number of reasons](../development/feature_flags/index.md#when-to-use-feature-flags), such as: - To test the feature. - To get feedback from users and customers while in an early stage of the development of the feature. - To evaluate users adoption. -- To evaluate how it impacts GitLab's performance. +- To evaluate how it impacts the performance of GitLab. - To build it in smaller pieces throughout releases. Features behind flags can be gradually rolled out, typically: @@ -36,7 +36,7 @@ error, it's very important that you [**provide feedback**](https://gitlab.com/gi as possible so we can improve or fix it while behind a flag. When you upgrade GitLab to an earlier version, the feature flag status may change. -CAUTION: **Caution:** +WARNING: Features deployed behind feature flags may not be ready for production use. However, disabling features behind flags that were deployed enabled by default may also present a risk. If they're enabled, we recommend |