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

Match Travelling Ruby (2.2.2) #80

Merged
merged 1 commit into from
Feb 2, 2016
Merged

Conversation

geoffharcourt
Copy link
Collaborator

This reverts commit 95ac59c. We are
going to track with Travelling Ruby at the minor version level as long
as that is our distribution solution.

Close #78.

@bernerdschaefer
Copy link
Contributor

Looks good when CI is green.

For reference, it looks like we can track phusion/traveling-ruby#62 for updates on 2.3.0.

@geoffharcourt
Copy link
Collaborator Author

Thanks @bernerdschaefer I'm not sure why this is failing on CI at the moment, I can't reproduce locally. Will look into it shortly.

@geoffharcourt geoffharcourt force-pushed the gh-match-travelling-ruby branch from 982e952 to d662c0e Compare February 2, 2016 15:50
@geoffharcourt geoffharcourt changed the title Revert "Update Ruby to version 2.3.0" Match Travelling Ruby (2.2.2) Feb 2, 2016
@geoffharcourt geoffharcourt force-pushed the gh-match-travelling-ruby branch from d662c0e to d97b2b4 Compare February 2, 2016 15:51
This change falls back to Ruby 2.2.2. In 95ac59 we moved to Ruby 2.3.0,
but Parity's preferred distribution is through a Travelling Ruby
executable, so we are going to track with their latest version.

Close #78.
@geoffharcourt geoffharcourt force-pushed the gh-match-travelling-ruby branch from d97b2b4 to 5e74e0e Compare February 2, 2016 16:13
@geoffharcourt geoffharcourt merged commit 5e74e0e into master Feb 2, 2016
@geoffharcourt geoffharcourt deleted the gh-match-travelling-ruby branch February 2, 2016 21:35
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.

2 participants