[SERVER-60213] Standardize when to use and remove feature flags in the lifecycle of a project Created: 24/Sep/21 Updated: 02/Mar/23 Resolved: 06/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Backlog - Replication Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | milestone-2, pm-2821-milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
Currently, projects differ in how they handle feature flags, with some removing the flag at end of project and replacing it with specific FCV checks, while other projects leave the flag until the next LTS release. Since feature flags allow us better control over FCV usage, we should standardize that projects leave all feature flags in until the next LTS release.
This improvement will make FCV code more consistent throughout the code base, simplifying the process of triaging and resolving potential issues when removing FCV code. This will likely require buy-in with other teams. |
| Comments |
| Comment by Huayu Ouyang [ 06/Feb/23 ] |
|
I think this was actually standardized and documented in the README as part of |