SERVER-32412 adds FCV 4.0, and SERVER-32741 bumps the default value of the FCV parameter to 3.6. Once 3.4 to 3.6-specific code is pulled out (or identified), all remaining pre-existing references to the "upgraded" FCV value in the code can be bumped from 3.6 to 4.0 and references to the "downgraded" FCV value can be bumped from 3.4 to 3.6. This includes updating FeatureCompatibilityVersion::setIfCleanStartup to store the "upgraded" FCV in the featureCompatibilityVersion document on clean startup.
- has to be done after
-
SERVER-32460 Determine and remove featureCompatibilityVersion-dependent Platforms code behavior that is only relevant to the 3.4-3.6 transition
- Closed
-
SERVER-32461 Determine and remove featureCompatibilityVersion-dependent Query code behavior that is only relevant to the 3.4-3.6 transition
- Closed
-
SERVER-32463 Determine and remove featureCompatibilityVersion-dependent Sharding code behavior that is only relevant to the 3.4-3.6 transition
- Closed
-
SERVER-32466 Determine and remove featureCompatibilityVersion-dependent Replication code behavior that is only relevant to the 3.4-3.6 transition
- Closed
- has to be done before
-
SERVER-31985 Modify and re-enable multiversion tests disabled until featureCompatibilityVersion is bumped to 3.8
- Closed
-
SERVER-31993 Unblacklist add_invalid_shard.js and new_mongos_old_mongod_wire_version_clash.js in the multiversion suite when the minimum wire version is bumped for 3.7
- Closed
-
SERVER-32272 Remove all 3.4 to 3.6-specific featureCompatibilityVersion-dependent behavior from Storage code
- Closed
-
SERVER-33045 Remove fcvLock from shardCollection after FCV 3.4 is removed
- Closed
-
SERVER-33179 Remove featureCompatibilityVersion 3.4 once it is no longer in use.
- Closed
- is related to
-
SERVER-32741 Bump the default value of the featureCompatibilityVersion parameter to 3.6
- Closed
- related to
-
SERVER-33945 Update must upgrade comment to use most recent version values
- Closed