Details
-
Task
-
Status: Blocked
-
Major - P3
-
Resolution: Unresolved
-
None
-
None
-
None
-
Replication
-
Repl 2022-12-12, Repl 2022-12-26, Repl 2023-01-09, Repl 2023-01-23, Repl 2023-02-06, Repl 2023-02-20, Repl 2023-03-06, Repl 2023-03-20, Repl 2023-04-03, Repl 2023-04-17, Repl 2023-05-01
Description
Once all of the database teams have removed their old upgrade/downgrade code with references to 5.x versions, we will need to remove the FCV constants for those versions as well.
Attachments
Issue Links
- depends on
-
SERVER-69332 Remove Feature Flag for PM-1942
-
- Open
-
-
SERVER-69310 Remove Feature Flag for PM-2364
-
- Backlog
-
-
SERVER-69347 Remove Feature Flag for PM-234
-
- Backlog
-
-
SERVER-69317 Remove Feature Flag for PM-2213
-
- Closed
-
-
SERVER-61481 Remove check in dropIndexes command that no index builds are in progress for the collection once kLastLTS is 6.0
-
- Closed
-
-
SERVER-62375 Remove upgrade/downgrade code for internal transactions
-
- Closed
-
-
SERVER-62496 Remove FCV-gated capped collection restriction once kLastLTS is 6.0
-
- Closed
-
-
SERVER-64042 Remove FCV check within coll mod for resizing capped collections once 6.0 is released.
-
- Closed
-
-
SERVER-67248 Remove any additional references to 5.x FCV constants
-
- Closed
-
-
SERVER-69320 Remove Feature Flag for PM-2188
-
- Closed
-
-
SERVER-58743 Remove rpc::ShardingMetadata
-
- Closed
-
-
SERVER-61545 Remove feature compatibility version casing around TTL indexes on capped collections
-
- Closed
-
- is depended on by
-
SERVER-67234 Ban uses of FCV constants for FCV checks
-
- Closed
-