Ruby 2.7 support
|Assignee:||Go MAEDA||% Done:|
Ruby 2.7.0 is going to be released on 2019-12-25.
#3 Updated by Seiei Miyagi about 2 years ago
With ruby 2.7, following tests failed.
bin/rails test test/functional/timelog_report_test.rb:262 bin/rails test test/functional/timelog_report_test.rb:308
I send a pull request to ruby/csv to fix it.
The pull request is merged but not released yet.
#13 Updated by Go MAEDA over 1 year ago
Since the latest Ruby 2.7.2 disables all deprecation warnings by default, I think Redmine can support Ruby 2.7 if it ignores 2.7.0 and 2.7.1.
The reason why Redmine still stays in Ruby 2.6 is that huge numbers of deprecation warnings are displayed while runnning tests. The problem is resolved by the change of Ruby 2.7.2, so I think it is no problem to use Ruby 2.7.2 now.
diff --git a/Gemfile b/Gemfile index 0cfe10e49..24c85b341 100644 --- a/Gemfile +++ b/Gemfile @@ -1,6 +1,6 @@ source 'https://rubygems.org' -ruby '>= 2.3.0', '< 2.7.0' +ruby '>= 2.3.0', '< 2.8.0' gem 'bundler', '>= 1.12.0' gem 'rails', '188.8.131.52' diff --git a/doc/INSTALL b/doc/INSTALL index f4374dae1..137088290 100644 --- a/doc/INSTALL +++ b/doc/INSTALL @@ -7,7 +7,7 @@ http://www.redmine.org/ == Requirements -* Ruby 2.3, 2.4, 2.5, 2.6 +* Ruby 2.3, 2.4, 2.5, 2.6, 2.7 (except for 2.7.0 and 2.7.1) * Bundler >= 1.12.0 * A database:
#16 Updated by Go MAEDA over 1 year ago
Enziin System wrote:
If Ruby 2.7 (excluding 2.7.0 and 2.7.1) then Redmine NOT support Ruby 2.7 version, still Ruby 2.6x
Although Redmine does not support Ruby 2.7.0 and 2.7.1 but supports 2.7.2 or higher. This is related to the following issues:
#19 Updated by Adrien Crivelli 11 months ago
Thank you for the patch.
Unfortunately the patch was ready 4 months ago, but it has not been released yet, and will only be released as part of 4.2.0. According to the roadmap, 4.2.0 is at 80% with 42 opened issues. It could still be weeks, if not months, before we see this patch released.
I would like to suggest to consider to make releases slightly more often. Last release was almost 1 year ago. In fact with 210 issues 4.2.0 is on the biggest version in recent years. What about splitting versions in two to have approximately two releases per year ?
So I'd suggest to release the first half of 4.1.0 right now, and postpone what is not ready in the next version.
What do you think ?