Feature #25538

Drop support Ruby 2.2.1 and ealier

Added by Toshi MARUYAMA 17 days ago. Updated 14 days ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:4.0.0
Resolution:

0001-Dropped-Ruby-2.1-and-earlier-support.patch Magnifier (3.26 KB) Go MAEDA, 2017-04-07 10:30

History

#1 Updated by Toshi MARUYAMA 17 days ago

#2 Updated by Toshi MARUYAMA 17 days ago

  • Blocks Defect #22335: Images with non-ASCII file names are not shown in PDF added

#3 Updated by Toshi MARUYAMA 17 days ago

  • Description updated (diff)

#4 Updated by Go MAEDA 16 days ago

+1

#5 Updated by Go MAEDA 16 days ago

This is a patch to drop ruby 2.1 and earlier support by removing RUBY_VERSION condition expressions.

#6 Updated by Fernando Hartmann 16 days ago

Hi, this will block my upgrade to 3.4.0 in my Ubuntu 14.04 LTS and OpenSuSE 42.2# and probably other distros.

Shouldn't this be put in 4.0.0 like #23630 and #19755 ?
Given some more time to users to plan system upgrades ?

#7 Updated by Holger Just 16 days ago

I agree, dropping support for Ruby versions should probably be done in a major version instead.

That said, dropping Ruby 1.9.3 support is probably a good idea in the short-to-middle term since it is seriously old and not supported by the Ruby language team for quite some time. For other versions, I'd be actually more careful.

  • Ubuntu 14.04 LTS defaults to Ruby 1.9.3, but also ships with Ruby 2.0. Ubuntu 16.04 LTS ships with Ruby 2.3 by default.
  • Debian stable (Jessie) currently ships with Ruby 2.1. The next stable (which is just around the corner) will ship with Ruby 2.3
  • RHEL/CentOS 7 ships with Ruby 2.0 currently, RHEL/CentOS 6 still ships Ruby 1.8.7.
  • OpenSuSE 42 ships with Ruby 2.1

Given this landscape, in order to provide the broadest possible support for existing users, I'd propose to only drop Ruby 1.9.3 support in the short term (if at all, see below). I understand that is is desirable to also drop at least Ruby 2.0 but this would seriously inconvenience many people who have to use older Ruby versions from their upstream vendors. Thus, I'd propose to only follow this approach now if the gain of not supporting older Ruby 2.x versions is actually significant.

In general, I think that the removal of supported Ruby versions should be done in a major version bump only. With the release of Redmine 4, I'd be quite happy if only Ruby >= 2.2 would be supported. Given that Rails 5 requires Ruby >= 2.2.2 anyway, this is probably a given requirement. Until then, I'd propose we still support the existing Ruby versions in all existing and future 3.x-stable branches.

#8 Updated by Jean-Philippe Lang 15 days ago

  • Target version deleted (3.4.0)

#9 Updated by Toshi MARUYAMA 15 days ago

#10 Updated by Toshi MARUYAMA 15 days ago

  • Blocks deleted (Defect #22335: Images with non-ASCII file names are not shown in PDF)

#11 Updated by Go MAEDA 14 days ago

  • Subject changed from Drop support Ruby 1.9.3 and 2.0 to Drop support Ruby 2.2.1 and ealier
  • Target version set to 4.0.0

Also available in: Atom PDF