[SERVER-69117] Investigate pre-creating a feature flag for non-project tickets that need feature flag gating Created: 24/Aug/22 Updated: 21/Feb/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Huayu Ouyang | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pm-2821-milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
From PM-2821, we are standardizing that anything that used to use an FCV constant check should instead use feature flag gating. This means that even one-off non-project tickets will all have to create their own feature flag and enable it for a certain version, which creates more overhead for engineers. Instead, we could look into creating one "default" feature flag that is enabled by default starting on each version that’s currently allowed, and have those non-project tickets use those feature flags for feature flag gating. That way it would be an easier interface/example for other server engineers to use. |