Merge branch...

Merge branch '1041-rca-board-functionality-broken-in-self-managed-16-7-ff-docs-update' into 'master' 

Docs update - Remove feature flag

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/141837



Merged-by: Kushal Pandya <kushal@gitlab.com>
Approved-by: John Hope <jhope@gitlab.com>
Approved-by: Kushal Pandya <kushal@gitlab.com>
Reviewed-by: Rémy Coutable <remy@rymai.me>
Reviewed-by: Kushal Pandya <kushal@gitlab.com>
Reviewed-by: John Hope <jhope@gitlab.com>
Reviewed-by: Eduardo Sanz García <esanz-garcia@gitlab.com>
Co-authored-by: Florie Guibert <fguibert@gitlab.com>

doc/development/feature_flags/index.md

@@ -65,6 +65,11 @@ When the feature implementation is delivered over multiple merge requests:
    - Add a [changelog entry](#changelog).
    - Remove the feature flag to enable the new behavior, or flip the feature flag to be **enabled by default** (only for `ops` and `beta` feature flags).
 
+When the feature flag removal is delivered over multiple merge requests:
+
+1. The value change of a feature flag should be the only change in a merge request. As long as the feature flag exists in the codebase, both states should be fully functional (when the feature is on and off).
+1. After all mentions of the feature flag have been removed, legacy code can be removed. Steps in the feature flag roll-out issue should be followed, and if a step needs to be skipped, a comment should be added to the issue detailing why.
+
 One might be tempted to think that feature flags will delay the release of a
 feature by at least one month (= one release). This is not the case. A feature
 flag does not have to stick around for a specific amount of time