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

Drop ruby 1.8-1.9-2.0-2.1-2.2-2.3 support #247

Conversation

deivid-rodriguez
Copy link
Contributor

Hello! 👋

What do you think about dropping support for very old rubies such as 1.8.7 or 1.9.3?

@deivid-rodriguez deivid-rodriguez changed the title Drop ruby 1.8 and ruby 1.9 support Drop ruby 1.8-1.9-2.0-2.1-2.2-2.3 support Jan 18, 2020
@deivid-rodriguez
Copy link
Contributor Author

Hello! Any interest on this? :)

@grosser
Copy link

grosser commented May 29, 2020

@korny this too ideally 🎉

@korny
Copy link
Member

korny commented May 29, 2020

Thank you for the cleanup suggestions! The plan is to drop support for older ruby versions in version 2.0, but not before. Is there anything here that is actually a problem for current users?

@korny korny added this to the 2.0 milestone May 29, 2020
@korny korny self-assigned this May 29, 2020
@deivid-rodriguez
Copy link
Contributor Author

deivid-rodriguez commented May 29, 2020

No idea since I don't use old rubies, I might work or it might not.

What I know is that the library does not pass its own tests on both ruby 1.8 and ruby 1.9. My intention when opening this PR was to get CI green, but since there was many other rubies that have already reached their End of Life, I figured I would go all the way and drop support for everything not supported upstream.

Users of old rubies can still stick to previous versions, and version managers will gracefully handle that, so I don't see any issues with dropping support. But of course it's up to you! :)

@korny
Copy link
Member

korny commented May 30, 2020

What I know is that the library does not pass its own tests on both ruby 1.8 and ruby 1.9.

CI must be green, I agree. But it's the gems setup that is breaking every few months, not CodeRay. I fixed it again on master :)

@deivid-rodriguez
Copy link
Contributor Author

Sure, fixing the CI also works, I just thought it would be easier to just kill the whole thing 😆.

Thanks for fixing it and for the release :)

@deivid-rodriguez
Copy link
Contributor Author

I rebased this PR in case you're ready to go to 2.0 :)

@codeclimate
Copy link

codeclimate bot commented May 30, 2020

Code Climate has analyzed commit a5d9fe7 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (80% is the threshold).

This pull request will bring the total coverage in the repository to 77.3% (-0.2% change).

View more on Code Climate.

@deivid-rodriguez
Copy link
Contributor Author

Also, note that you have fixed CI for ruby 1.9, but ruby 1.8 is still broken. I don't know a single library testing successfully against ruby 1.8 in 2020, it sounds like an interesting challenge :)

@deivid-rodriguez
Copy link
Contributor Author

Actually, I do! RSpec does it: https://travis-ci.org/github/rspec/rspec-core. Maintenance giants there!

@deivid-rodriguez
Copy link
Contributor Author

I don't like to let PRs hang so long, so I'll close this!

@deivid-rodriguez deivid-rodriguez deleted the drop_old_rubies_support branch January 13, 2022 11:26
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

3 participants