-
Notifications
You must be signed in to change notification settings - Fork 15
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
Decide which ruby versions to support #48
Comments
I'd boldly say that 2.0 should go away too. |
I'd still say go with ruby 2+ for now and then drop support by the end of the year. |
Since 1.9.3 is the only one that is making us take extra effort to write For 2.0 we haven't had any problems yet, I think. Let us keep the tests for On Wed, Jun 1, 2016, 1:25 PM Sameer Deshmukh notifications@github.com
|
Let's drop 1.9.3. since it doesn't receive security patches. We can Sent from my mobile phone.
|
Seems 2.0 also doesn't receive security patches. We should drop 2.0 as well. |
In travis, we test,
We initially included these because these were the ones supported in NMatrix I think.
Since official support for 1.9.3 is stopped including security patches, I'm okay with dropping 1.9.3. What do you think?
@zverok, @certik, @abinashmeher999, @rajithv, @MohawkJohn, @v0dro
The text was updated successfully, but these errors were encountered: