Skip to content

Update branches for new master-next scheme. #7427

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 13, 2017

Conversation

bob-wilson
Copy link
Contributor

No description provided.

Combine the "next" and "next-upstream" checkout schemes since the new
approach for maintaining master-next is to building against the
"upstream-with-swift" Clang/LLVM branches. We do not plan to use the
"stable-next" branches anymore. (We can delete those branches after
this transition has had time to settle out.) I have also merged the
"upstream" scheme with "next-upstream" because building the combination
of branches previously in the scheme is not something we expect to work
now.
@bob-wilson
Copy link
Contributor Author

@gottesmm Can you review this?

@gottesmm
Copy link
Contributor

LGTM! I would just talk with Mishal about removing the preview branches. @shahmishal How does that part look to you?

@gottesmm
Copy link
Contributor

@swift-ci Please smoke test

@bob-wilson
Copy link
Contributor Author

Thanks. (The smoke tests don't exercise this script, do they?)

@gottesmm
Copy link
Contributor

@bob-wilson While they do not exercise this specific scheme, they will make sure that normal usage still works [which is what I was trying to test = )]

@shahmishal
Copy link
Member

LGTM.

@gottesmm gottesmm merged commit 5ca9aae into swiftlang:master Feb 13, 2017
@bob-wilson bob-wilson deleted the update-checkout-next branch March 22, 2017 01:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants