Skip to content
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

Deprecate LLVM 3.6 OSX support #1502

Merged
merged 1 commit into from
Jan 7, 2017
Merged

Deprecate LLVM 3.6 OSX support #1502

merged 1 commit into from
Jan 7, 2017

Conversation

SeanTAllen
Copy link
Member

No longer available via homebrew.

No longer available via homebrew.
@SeanTAllen
Copy link
Member Author

I only deprecated support for LLVM 3.6 for OSX.

I talked to @sylvanc and he is ok with deprecated 3.6 for Linux and Windows as well.

@ponylang/committer anyone object to deprecating across the board?

@SeanTAllen SeanTAllen added changelog - changed Automatically add "Changed" CHANGELOG entry on merge needs discussion during sync labels Jan 7, 2017
@SeanTAllen
Copy link
Member Author

This passed and everyone has indicated they are in favor of removing for OSX, merging down. We can discuss if we drop LLVM 3.6 in general and remove from Linux and Windows if we decide to.

@SeanTAllen SeanTAllen merged commit 8112404 into master Jan 7, 2017
ponylang-main added a commit that referenced this pull request Jan 7, 2017
@SeanTAllen SeanTAllen deleted the deprecate-llvm-36 branch January 7, 2017 04:21
@sylvanc
Copy link
Contributor

sylvanc commented Jan 9, 2017

I would vote yes to deprecating LLVM 3.6 on all platforms. Staying relatively current on our dependencies (especially our most important dependency, LLVM) will save us a lot of work down the road. And 3.6 is "old enough" now, in the sense that no Linux distribution that I know of does not have access to 3.7.

@Praetonus
Copy link
Member

I vote yes as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog - changed Automatically add "Changed" CHANGELOG entry on merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants