Require that some feature flag toggles use the change management process
Why is this change being made?
Proposed update to the GitLab.com Change Management process to include some conditions under which feature flag toggles should be accompanied by a production change management issue.
If there is broad agreement on this change, we should also update https://docs.gitlab.com/ee/development/feature_flags/controls.html#process as a next step, with a reference to this policy.
Author Checklist
-
Provided a concise title for the MR -
Added a description to this MR explaining the reasons for the proposed change, per [say-why-not-just-what][transparency] -
Assign this change to the correct DRI - If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
- If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in [#mr-buddies][mr-buddies-slack].
- If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping
@gl-static-site-editor
in a comment for a review and merge. For example changes to.gitlab-ci.yml
, JavaScript/CSS/Ruby code or the layout files.
cc @marin @brentnewton @dawsmith @albertoramos @amyphillips @rnienaber @AnthonySandoval
Edited by Andrew Newdigate