Document upgrade v1 to v2 considerations #1773
Draft
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Andy and I have been discussing how a user might upgrade their v1 sites to v2 sites.
This draft PR summarizes some of our discussions in a doc to run by the team, to ask for feedback and opinions.
When people have a chance to take a look, it will be great to hear thoughts / feedback.
If time permits in this Thursday's skupper community meeting, we're planning to ask for feedback in that meeting.
Posting as a draft PR, in case people have comments to add to the PR ahead of the meeting...