Remove LegacyUpgrader #91
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
elenadimitrova
force-pushed
the
maintenance/remove-legacy-upgraders
branch
from
8d333d8
to
6e3f7c3
Compare
juniset
approved these changes
Apr 8, 2020
elenadimitrova
force-pushed
the
maintenance/remove-legacy-upgraders
branch
from
ab9546f
to
3ce8281
Compare
elenadimitrova
force-pushed
the
maintenance/remove-legacy-upgraders
branch
from
fc1b5ad
to
a18270b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ModuleManager-based upgrade approach was used up and including release 1.3. Since release 1.4 we've maintained theLegacyUpgraderwhich supported direct upgrade from versions prior to 1.4. here in release 1.6 we decommission this capability, setting theBACKWARD_COMPATIBILITYto 1 to offer upgrade support from 1.4 -> 1.6 only (1.5 had no module upgrades needed).