[SERVER-52026] Create feature flag for API version testing Created: 30/Oct/20  Updated: 06/Dec/22  Resolved: 04/Nov/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task
Reporter: Connie Chen Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Participants:

 Description   

Create the feature flag for this project



 Comments   
Comment by Samyukta Lanka [ 04/Nov/20 ]

I agree that a feature flag is unnecessary for this project. There shouldn't be significant behavioral changes and I agree that it would be safe to release at any point without such a flag (and we'll keep this in mind as we review changes). I'm okay to close both this ticket and SERVER-52329.

Comment by A. Jesse Jiryu Davis [ 04/Nov/20 ]

Correct, we anticipate no significant behavior changes, and we'll use all existing tests to validate that.

Comment by Judah Schvimer [ 04/Nov/20 ]

The main question for me is "would it be safe to release at any point without a feature flag?". For this project the answer should be yes, it would always be safe to release, so I agree we can close it. Is that correct?

Comment by A. Jesse Jiryu Davis [ 04/Nov/20 ]

I guess we make "create feature flag" tickets for every project, but I think we should close this one (and SERVER-52329).

This is a testing-only project. On the one hand, there will be server code changes: we'll convert all API Version 1 commands to IDL. On the other hand, our intention is to avoid any significant behavior changes, so I don't think feature flagging is necessary. Feature flagging would also be extremely difficult for this change, and probably increase risk rather than decreasing it. samy.lanka and judah.schvimer, what do you think?

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