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

Support Ruby 2.3 or later #62

Closed
wants to merge 1 commit into from
Closed

Support Ruby 2.3 or later #62

wants to merge 1 commit into from

Conversation

mlarraz
Copy link

@mlarraz mlarraz commented May 22, 2016

Ruby since 2.0 has become a lot more stable, and there is no reason this should not be using the newest version.

This also simplifies some logic, since all we really care about is whether RUBY_VERSION is less than 2.3.0 or not.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 94.559% when pulling ec45e34 on mlarraz:ruby_2.3 into 5bf28ab on aws:master.

Ruby since 2.0 has become a lot more stable, and there is no reason this should not be using the newest version.

This also simplifies some logic, since all we really care about is whether RUBY_VERSION is less than 2.3.0 or not.
@coveralls
Copy link

coveralls commented May 22, 2016

Coverage Status

Coverage increased (+0.01%) to 94.573% when pulling c5e04e8 on mlarraz:ruby_2.3 into 5bf28ab on aws:master.

@dgolja
Copy link

dgolja commented Jun 2, 2016

Hmmm why again hardcoding the ruby version in the scripts ? Why just not check the version on runtime ?

@cbernadino
Copy link

cbernadino commented Jun 23, 2016

Just curious if anyone knows the status of this commit? Eager to get an updated agent installed on the latest Ubuntu build.

@mlarraz
Copy link
Author

mlarraz commented Jun 24, 2016

Isn't this not necessary now that c554a11 is in master?

@suryanarayanan
Copy link
Contributor

I'm going to close this PR since it suffers from the same problem as we have today with ruby version 2.0. We are working on releasing a change that doesn't pin the agent to a specific version of ruby. I'll post more updates once we start the rollout.

@dgolja
Copy link

dgolja commented Jul 16, 2016

why close the issue if it's not solved ? Why not to wait for the solution and then close it ?

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.

None yet

5 participants