-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Internal Code
-
None
-
Sharding
-
Fully Compatible
-
Sharding 2017-09-11, Storage 2017-10-23
To facilitate cleaning up dead code after splitting the master development branch from the 3.6 release branch, comparisons against serverGlobalOptions.featureCompatibility.version should be restricted to asking the question "is the current version 3.4?" By making this restriction, when we remove the constants for v3.4 in the development branch and add the v3.8 constants instead, the compiler will direct our developers to branches that are now always-taken or never-taken.
Note, this task does not include auditing comparisons against the feature compatibility version to ensure that they are race-free or otherwise correct.
- depends on
-
SERVER-31315 expose the four distinct upgrade/downgrade states in serverGlobalParams.featureCompatibility
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
SERVER-31783 Secondaries may generate a UUID for a replicated collection on their own while upgrading to fCV=3.6
-
- Closed
-