Add the skeleton of a migration roadmap article #46
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
dempseyatgithub
requested review from
hborla,
ktoso,
mattmassicotte and
shahmishal
as code owners
Member
I was able to convert this to a draft! I'll look into why you weren't able to do that yourself. |
Collaborator
|
We've spoken about publishing guidance like this. I think it could be really valuable. |
Closed
Merged
Collaborator
|
@dempseyatgithub how to do you feel about closing this in favor of #72 ? I'd love to hear your thoughts on that article! |
Contributor
|
Wanted to review but this seems borked somehow? Diff is empty
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
There is a lot of great information in the migration guide already.
However, there are a lot of options and combinations, developers sticking with a 5.x compiler for the time being, developers moving to the 6.0 compiler, but sticking with Swift 5 language mode, etc.
I thought it would be useful for developers to have a high level roadmap that helps them figure out what situation their projects are in and what migration steps they can take depending on their situation.
This is just a skeleton of an article, I haven't had a chance to flesh it out, but thought a PR would make a good place for discussion and potentially PR revisions by others.
(I tried to mark this as a draft PR since it isn't a fully-formed article yet, but that option does not seem available.)