channeldb: revert to prior migration policy #3597
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
|
Bless you sir. |
|
🙏🏾 thanks to all that gave feedback on this topic!
…On Wed, Oct 16, 2019, 8:49 PM Brian Lockhart ***@***.***> wrote:
Bless you sir.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#3597?email_source=notifications&email_token=AAHTWLSH4DPEMO6ALJUU7NDQO5O4VA5CNFSM4JAEOQD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBNRONQ#issuecomment-542840630>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHTWLTW2E2JU6IXWBLQ6Z3QO5O4VANCNFSM4JAEOQDQ>
.
|
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.
In this commit, we revert #3485, thereby reverting to our existing migration policy. The prior stricter policy created a large burden on applications that package
lndas they're forced to deploy special code to handle certain upgrade paths. In addition, it was realized that the policy was most damaging to mobile deployments as it's customary for users to skip versions, making the stricter upgrade policy difficult to manage without dramatically affecting the end user.