docs: Comprehensively update release branch creation guide#1082
Open
docs: Comprehensively update release branch creation guide#1082
Conversation
Completely revise ReleaseProcess.md with detailed step-by-step instructions for creating new release branches: - Document all required updates to default.xml (default revision, LLVM project revision) - Detail build-toolchain.yml updates (swift_version, untagged repo revisions, snapshot job configuration) - Document dual-workflow structure: release branches use local references for direct testing, main uses @release/X.Y for scheduled builds - Add section on testing changes to release branches without requiring workflow modifications
Steelskin
requested review from
compnerd,
hjyamauchi,
mhegazy,
speednoisemovement and
sundresh
speednoisemovement
approved these changes
Jan 29, 2026
Collaborator
speednoisemovement
left a comment
speednoisemovement
left a comment
There was a problem hiding this comment.
LGTM % comment (but I've never done one of these e2e, so grain of salt)
| create_release: ${{ github.event_name == 'schedule' }} | ||
| create_snapshot: ${{ github.event_name == 'schedule' }} | ||
| # Infrastructure/Runners | ||
| windows_x64_default_runner: <your-x64-runner-label> |
Collaborator
There was a problem hiding this comment.
We also need to add "pinned" runner definitions (basically copy from main and rename). Example: thebrowsercompany/swift-build#324
Collaborator
Author
There was a problem hiding this comment.
This is public documentation and the pinned runners are an artifact of the downstream repository.
Collaborator
There was a problem hiding this comment.
Maybe just a note to make sure to capture runner state without specifics?
Collaborator
Author
There was a problem hiding this comment.
How about adding docs in the downstream repository also explaining how it differs from compnerd/swift-build?
compnerd
reviewed
Jan 29, 2026
hjyamauchi
approved these changes
Jan 29, 2026
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
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.
Completely revise ReleaseProcess.md with detailed step-by-step instructions for creating new release branches: