-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Upgrade/Downgrade
-
None
-
Fully Compatible
-
Storage 2018-01-01, Storage 2018-01-15, Storage 2018-01-29
In order to facilitate the development of 4.0-specific features, a 4.0 value should be added to the featureCompatibility enum and also should be an accepted input to the setFeatureCompatibilityVersion command. Transitions from 3.4 to 4.0 should be explicitly prohibited, as all 3.4-specific code will be removed as part of this project.
- has to be done before
-
SERVER-32729 Bump the replica set heartbeat version so a latest-FCV primary does not attempt to talk to a last-stable binary secondary
- Closed
- is related to
-
SERVER-32829 Re-enable multiVersion/set_feature_compatibility_version.js and update noPassthrough/feature_compatibility_version.js
- Closed