Remove migrations prior to 1.0.3.162 #5939
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
NicolasDorier
force-pushed
the
removemigrations
branch
from
33c5cf3
to
e9901b3
Compare
1 task
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.
This remove migrations code for instances which haven't updated since before
6 march 2020. (1.0.3.162)The implication is that anybody from version
1.0.3.161 or earlier(that is who didn't updated since the release of1.0.3.162the 6th march 2020), won't be able to migrate to 2.0 directly and will need to update to 1.13.x first.We don't strictly need it, but time to time, those old migrations give more work when we refactor, and they'll always grow over time. I believe 4-5 years is good enough support, and we should clean up home then.