Feature #31500
closedRuby 2.7 support
0%
Related issues
Updated by Go MAEDA over 5 years ago
- Copied from Feature #30118: Ruby 2.6 support added
Updated by Go MAEDA almost 5 years ago
- Related to Patch #32527: Fix ruby 2.7 warning: given argument is nil; this will raise a TypeError in the next release added
Updated by Seiei Miyagi almost 5 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.
https://github.com/ruby/csv/pull/111
The pull request is merged but not released yet.
Updated by Go MAEDA almost 5 years ago
- Related to Patch #32542: Fix ruby 2.7 warning: The last argument is used as the keyword parameter added
Updated by Go MAEDA almost 5 years ago
- Related to Defect #32752: Ruby 2.7: Remove deprecated URI.escape/unescape added
Updated by Marius BÄ‚LTEANU almost 5 years ago
- Related to Patch #32906: Update i18n (~> 1.8.2) added
Updated by Go MAEDA almost 5 years ago
- Related to Patch #32907: Update capybara (~> 3.31.0) added
Updated by Go MAEDA over 4 years ago
- Related to Defect #33021: [v.4.0.5-stable] Internal Server Error 500 when accessing 'repository' tab added
Updated by Jeremy Bailey over 4 years ago
https://github.com/ruby/csv/pull/111 was merged in November 2019, but it seems that ruby/csv hasn't yet been updated since 3.1.2 in October 2019.
Updated by Ludovic Andrieux over 4 years ago
ruby/csv 3.1.3 is released with the fix : https://github.com/ruby/csv/releases/tag/v3.1.3
Updated by Anatol Pomozov about 4 years ago
Hi folks,
Ruby 2.7 released almost a year ago. It would be great if useful tools redmine finally became supported at this latest stable version of Ruby.
Could anyone please give an update on the current status of this activity?
Updated by Xavier Maquil about 4 years ago
Any news about release for 2.7 support (Ubuntu 20.04.1 has it build in)
Updated by Go MAEDA about 4 years 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', '5.2.4.4'
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:
Updated by Go MAEDA about 4 years ago
- Status changed from New to Closed
- Assignee set to Go MAEDA
- Resolution set to Fixed
Redmine supports Ruby 2.7 (excluding 2.7.0 and 2.7.1) after r20150.
Updated by Enziin System about 4 years ago
If Ruby 2.7 (excluding 2.7.0 and 2.7.1) then Redmine NOT support Ruby 2.7 version, still Ruby 2.6x
In the Gemfile:
ruby '>= 2.3.0', '< 2.7.0'
To
ruby '>= 2.3.0', '<= 2.7.0'
Updated by Go MAEDA about 4 years 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:
Updated by Enziin System about 4 years ago
Ok, thanks!
In the above comment, you said "I think it is no problem to use Ruby 2.7.2 now"
Redmine run passed all tests on Ruby 2.7.2, isn't it?
Updated by Go MAEDA about 4 years ago
Enziin System wrote:
Redmine run passed all tests on Ruby 2.7.2, isn't it?
Yes. Redmine on Ruby 2.7.2 passes all tests without warnings.
Updated by Adrien Crivelli over 3 years 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 ?
Updated by Go MAEDA over 3 years ago
- Related to Defect #35135: FrozenError when new LDAP users try to login added
Updated by Go MAEDA over 3 years ago
- Related to Defect #35441: Inline image in Textile is not displayed if the image URL contains ampersands added