Add a known limitation about downgrades to 1.1.0 not working #2095
Conversation
This file contains hidden or 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
|
This change is |
|
+@bdarnell to make sure the terminology around versions (e.g. v1.1 vs v1.1.0) is reasonable, since @Amruta-Ranade isn't sure and @jseldess is out right now. |
|
Review status: 0 of 1 files reviewed at latest revision, all discussions resolved, some commit checks failed. Comments from Reviewable |
a-robinson
force-pushed
the
downgrade11
branch
from
35dd4ea to
1acf454
Compare
a-robinson
commented
Oct 24, 2017
There was a problem hiding this comment.
Slightly simplified the first sentence at @Amruta-Ranade's offline request.
jseldess
approved these changes
Oct 24, 2017
There was a problem hiding this comment.
LGTM. We also call this out at the end of the "Finalize the upgrade" step.
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.
No description provided.