Commit bc82ae61 authored by Kati Paizee's avatar Kati Paizee

Merge branch 'dcouture-security-feature-flag' into 'master'

Add mentions of security in feature flag risks

See merge request gitlab-org/gitlab!73752
parents f77caca4 8763bdf0
...@@ -42,11 +42,15 @@ GitLab to an earlier version, the feature flag status may change. ...@@ -42,11 +42,15 @@ GitLab to an earlier version, the feature flag status may change.
Features that are disabled by default may change or be removed without notice in a future version of GitLab. Features that are disabled by default may change or be removed without notice in a future version of GitLab.
Data corruption, stability degradation, or performance degradation might occur if Data corruption, stability degradation, performance degradation, or security issues might occur if
you enable a feature that's disabled by default. Problems caused by using a default you enable a feature that's disabled by default. Problems caused by using a default
disabled feature aren't covered by GitLab support, unless you were directed by GitLab disabled feature aren't covered by GitLab support, unless you were directed by GitLab
to enable the feature. to enable the feature.
Security issues found in features that are disabled by default are patched in regular releases
and do not follow our regular [maintenance policy](../policy/maintenance.md#security-releases)
with regards to backporting the fix.
## Risks when disabling released features ## Risks when disabling released features
In most cases, the feature flag code is removed in a future version of GitLab. In most cases, the feature flag code is removed in a future version of GitLab.
......
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