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.

Sign up for GitHub

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

Jump to bottom

Drop support for ruby 2.0 (EOL'd March 2016), also possibly ruby 2.1? #61

Open
spovich opened this issue Dec 31, 2017 · 2 comments
Open

Drop support for ruby 2.0 (EOL'd March 2016), also possibly ruby 2.1? #61

spovich opened this issue Dec 31, 2017 · 2 comments

Comments

@spovich
Copy link
Contributor

spovich commented Dec 31, 2017

@kshnurov any concern about dropping ruby 2.0 support? It was EOL'd in early 2016.

We may also consider dropping ruby 2.1 since rails 5.0+ requires ruby 2.2+.

Thoughts?
@spovich spovich changed the title Drop support for ruby 2.0 (EOL'd March 2016), also possibly ruby 2.1 Drop support for ruby 2.0 (EOL'd March 2016), also possibly ruby 2.1? Dec 31, 2017
@kshnurov
Copy link
Owner

@spovich sure, we can drop them if they cause any problems, but I don't see any reasons for making it right now. Is there some?

@spovich
Copy link
Contributor Author

spovich commented Dec 31, 2017

I just noticed during gem updates that the latest rubocop only supports ruby 2.1+. Rubocop 0.50.0 is the last version supporting 2.0. It's definitely not a big deal :) I would like to add 2.4 and 2.5 to the travis matrix. I'll do that now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@spovich @kshnurov