-
Notifications
You must be signed in to change notification settings - Fork 13
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
guard-yard for ruby 1.8.7 #8
Comments
There was a big deal about the Ruby project dropping official support for 1.8.7 at the end of June 2013 since it is so old and we were up to Ruby 2.0.0 by that time (but now we are up to 2.1.0). Since then, Heroku has stepped up and offered to support security patches to 1.8.7 (and 1.9.2) through June 2014. But I would switch to Ruby 2.x sooner rather than later. The Ruby project plans to end support for 1.9.3 next year. |
I can totally understand dropping support for 1.8. Just curious why the ruby 1.9 limitation was enforced in the gemspec. Thanks. |
Ruby 1.9 is enforced in the gemspec as a way of indicating that the gem was not tested/verified on 1.8. My understanding was that this was a best practice. In my mind, this enforcement means a couple of things:
|
That makes a lot of sense.. Thanks for the response. |
It would nice to have a |
Absolutely. I'll add that to the README as well. |
This is an awesome project which helps me browse through yard documentation faster. Why does this gem require ruby 1.9.2 or greater? I am perfectly able to run this project in ruby 1.8.7.
The text was updated successfully, but these errors were encountered: