Add 6 months limit to FF lifecycle
What does this MR do and why?
Today we have a monthly report that is sent to each engineering manager indicating feature flags that are older than 2 milestones and need attention.
Given that each feature flag represents a technical debt and that there are many of these flags that are very old, we should have a time limit after which action is required.
This MR documents the existence of a feature flag monthly report and suggests a harder limit of 6 months after which we can take any of the following (or maybe more) actions:
- Enable the feature flag by default (if not done already) and remove it from the codebase.
- Convert it to a setting (instance/group/project) so people can opt-out/in.
- Back it off if still disabled and if deemed no longer necessary.
cc @avielle @cheryl.li @m_gill
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.