-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Upgrade/Downgrade
-
None
-
Fully Compatible
-
Sharding 2018-01-15, Sharding 2018-01-29
As part of the 3.8 upgrade/downgrade project, all upgrade/downgrade behavior that was specific to the transition between 3.4 and 3.6 should be removed. The storage team will oversee that all teams remove 3.4 to 3.6-specific upgrade/downgrade behavior in their respective projects. To facilitate this removal, the storage team would like each team to determine which upgrade/downgrade behavior is specific to the 3.4 to 3.6 transition and which is generic upgrade/downgrade behavior that should be preserved between releases. The storage team will update the generic upgrade/downgrade behavior locations to use the most up-to-date featureCompatibilityVersion values.
- has to be done before
-
SERVER-32597 Update "latest" FCV to be 4.0 and "last-stable" FCV to be 3.6.
- Closed
- is duplicated by
-
SERVER-29754 Remove checks for featureCompatibilityVersion k34 from causal consistency
- Closed
- is related to
-
SERVER-31553 Update multiversion tests on 3.6 and master branches
- 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
- related to
-
SERVER-32799 Remove FeatureCompatibility::setVersion call in SessionCatalogMigrationDestinationTest::setUp
- Closed
-
SERVER-33425 Remove unused SessionsCommandFCV34Status function
- Closed