adding explicit migration plans #1189
Open
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
heckj
force-pushed
the
migration-plan-specifics
branch
from
3e85e70 to
fd2da2e
Compare
This was referenced Oct 24, 2025
heckj
force-pushed
the
migration-plan-specifics
branch
from
fd2da2e to
09d4103
Compare
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.
Adds in explicit migration plans for swift.org content associated with the Swift Docs proposal
Motivation:
Feedback from the Swift core team asked for specific plans for status and update of the existing articles, alongside a layout that described what needed to be done and their ultimate disposition.
Modifications:
Revised the layout and details to break up the listing of existing files, establishing a table of files to migrate
related migration plans for Swift server guides broken out into #1201 and #1202
Result:
Revised proposal with more discrete migration plans to implement