[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:
Depends
depends on SERVER-67234 Ban uses of FCV constants for FCV checks Closed
Duplicate
duplicates SERVER-69139 Add documentation for PM-2821 Closed
Related
is related to SERVER-61967 Ban usages of transitionary FCVs in F... Closed
is related to SERVER-61970 Investigate removing references to FC... Closed
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 SERVER-69139: https://github.com/mongodb/mongo/blob/1662872fc08f60fbdc1c43597c7b16182e186588/src/mongo/db/repl/FCV_AND_FEATURE_FLAG_README.md#lifecycle-of-a-feature-flag

Generated at Thu Feb 08 05:49:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.