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

guard-yard for ruby 1.8.7 #8

Closed
nitinmohan87 opened this issue Jul 10, 2013 · 6 comments
Closed

guard-yard for ruby 1.8.7 #8

nitinmohan87 opened this issue Jul 10, 2013 · 6 comments

Comments

@nitinmohan87
Copy link

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.

@L2G
Copy link

L2G commented Feb 9, 2014

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.

@nitinmohan87
Copy link
Author

I can totally understand dropping support for 1.8. Just curious why the ruby 1.9 limitation was enforced in the gemspec. Thanks.

@panthomakos
Copy link
Owner

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:

  • Bugs that relate only to Ruby 1.8 will not be resolved.
  • The gem is not tested/verified on Ruby 1.9 and lower.

@nitinmohan87
Copy link
Author

That makes a lot of sense.. Thanks for the response.

@nitinmohan87
Copy link
Author

It would nice to have a Requirements section in the README to document this.

@panthomakos
Copy link
Owner

Absolutely. I'll add that to the README as well.

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

No branches or pull requests

3 participants