[6.0] Move main/6.0 windows Foundation builds to separate branch (#75073) #75092
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
|
@swift-ci please test |
|
How long do we plan to maintain the two branches of swift-corelibs-foundation? This will pose an issue when tagging both the nightly and release, unless we establish a different tagging scheme for the Windows branch. |
|
Closing now that this is no longer necessary and is being reverted from |
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.
Cherry pick of #75073
Explanation: Adds a new swift-corelibs-foundation checkout of the
windows/*branch and updates the windows build script to use this checkoutScope: Affects building Foundation on windows
Original PR: #75073
Risk: Minimal - this should have no impact until the standard and
windows/*branches divergeTesting: Testing done via swift-ci testing
Reviewer: @parkera