-
Notifications
You must be signed in to change notification settings - Fork 4
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
Should we support Ruby 2.x? #17
Comments
My opinion is to drop support for Ruby 2.x. We want to test against all versions of Ruby that we support. In addition, GEM (minitest, hoe), which is required by OCRAN, will also end support for Ruby 2.x in the near future. Since Ruby on Windows 3.0, strings in ARGV will be UTF-8 (https://bugs.ruby-lang.org/issues/13571). |
|
Ok, we can drop old Ruby Versions, but make a note in the changelog, so users will now which version still works? |
#17 We want to test against all versions of Ruby that we support. In addition, the gems 'minitest' and 'hoe', which are required by OCRAN, will also end their support for Ruby 2.x in the near future.
#17 Ruby 3.0 and later will be the target of the tests. x64-mingw32 is required in PLATFORMS for testing with Ruby 3.0.
#17 We want to test against all versions of Ruby that we support. In addition, the gems 'minitest' and 'hoe', which are required by OCRAN, will also end their support for Ruby 2.x in the near future.
Should we support Ruby 2,6?
The version of RubyGems attached to Ruby2,6 is 3.0.3.1 and the following warning is reported when running tests in CI:
Should we support Ruby 2,7?
Ruby 2.6 and 2.7 will no longer be supported from Bundler 2.5.
https://github.com/rubygems/rubygems/blob/master/bundler/CHANGELOG.md#breaking-changes
If we support Ruby 2.7, we will not be able to upgrade the version of Bundler.
The text was updated successfully, but these errors were encountered: