-
-
Notifications
You must be signed in to change notification settings - Fork 57
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 #78
Comments
Downgrading seems reasonable. In the future we may want to move off of Traveling Ruby but I think the easiest/correct change here is to downgrade. I'd love to hear @croaky and @tabfugnic's thoughts though. |
@JoelQ I agree with you. Since we are keeping to traveling ruby it makes sense to me to downgrade. Likewise I would hope that we can move off of that at some point. |
geoffharcourt
added a commit
that referenced
this issue
Feb 2, 2016
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
added a commit
that referenced
this issue
Feb 2, 2016
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
added a commit
that referenced
this issue
Feb 2, 2016
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In 95ac59c we updated to use Ruby 2.3.0. We probably need to downgrade this to 2.2.2 to match Travelling Ruby's latest version.
@JoelQ @tabfugnic @croaky thoughts? I'm open to other solutions if we don't think Traveling Ruby is the right solution, but thus far I think packaging the gem has been a big win.
The text was updated successfully, but these errors were encountered: