Skip to content

Update LLVM development policy #32006

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Jun 3, 2020
Merged

Update LLVM development policy #32006

merged 2 commits into from
Jun 3, 2020

Conversation

MForster
Copy link
Contributor

State explicitly that we want to eliminate all differences between
apple/master and llvm.org/master. All new LLVM development should happen
upstream.

@MForster
Update LLVM development policy
8326e11 
State explicitly that we want to eliminate all differences between
`apple/master` and `llvm.org/master`. All new LLVM development should happen
upstream.
rjmccall
rjmccall reviewed May 26, 2020
View reviewed changes
Copy link
Contributor

@rjmccall rjmccall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should cover both apple/master and swift/master.

@rjmccall
Copy link
Contributor

I think Ted should sign off on the final wording here.

@MForster
Copy link
Contributor Author

This should cover both apple/master and swift/master.

I think we said that for now the swift/master rules don't change. Are you asking to be explicit about that or are you suggesting to tighten those policies as well?

@rjmccall
Copy link
Contributor

This should cover both apple/master and swift/master.

I think we said that for now the swift/master rules don't change. Are you asking to be explicit about that or are you suggesting to tighten those policies as well?

I'd just forgotten that. We should be explicit, though.

@MForster
Submitting to swift/master-next is still allowed.
66c333d 
Add additional clarification that submitting to `swift/master-next` continues to be allowed.
@MForster
Copy link
Contributor Author

We should be explicit, though.

I've added a note to that effect.

@swiftlang swiftlang deleted a comment from swift-ci May 29, 2020
@swiftlang swiftlang deleted a comment from swift-ci May 29, 2020
@tkremenek
Copy link
Member

This looks great to me.

@tkremenek tkremenek merged commit 3ff520b into swiftlang:master Jun 3, 2020
@MForster MForster deleted the m/upstreaming-policy branch June 4, 2020 07:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rjmccall rjmccall rjmccall left review comments

@gribozavr gribozavr gribozavr approved these changes

@dexonsmith dexonsmith Awaiting requested review from dexonsmith

@tkremenek tkremenek Awaiting requested review from tkremenek

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@MForster @rjmccall @tkremenek @gribozavr