consider: Stop supporting upgrade from 1.4 and 1.5 . #540
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
WireBaron
approved these changes
Sep 20, 2022
epgts
changed the title
We are automating testing upgrades of binaries, but these, our two oldest versions, are hard to automate because: - We released no binaries for 1.4 - The deb for 1.5 was labeled 1.5.0 We could special case these, but requiring two upgrade steps (1st to 1.5.1 and 2nd to latest) is not unreasonable for users who are eight months behind. For issue #419
epgts
force-pushed
the
eg/drop-old-upgrade
branch
from
c66af09 to
5492205
Compare
|
We'll include this in 1.15.0 . |
|
This PR is being supplanted by #743 |
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.
We are automating testing upgrades of binaries, but these, our two oldest versions, are hard to automate because:
We could special case these, but requiring two upgrade steps (1st to 1.5.1 and 2nd to latest) is not unreasonable for users who are eight months behind.
For issue #419