Tracker #4656
closed
Added by Dominic Cleal about 10 years ago.
Updated over 5 years ago.
Description
Tracker for anything concerning Ruby 1.8.7 support, and being able to drop it. There are likely things in Foreman we can revert (gem pins, workarounds).
There was a short discussion on foreman-dev in 2013 about when we'd look to drop it:
https://groups.google.com/d/msg/foreman-dev/0TsJ9wxmUOQ/YpBdCi97ARgJ
The general consensus there and in other discussions has been to continue supporting 1.8 while it's been reasonable effort (pinning gems etc), and while none of our major dependencies (i.e. Rails, Fog) have dropped it. A move to Rails 4 would necessitate dropping 1.8.
- Plugins use deface < 1.0 at the moment, but >= 1.0 requires nokogiri ~> 1.6.0 which is incompatible with 1.8. We can then switch to deface 1.0 after dropping 1.8.
- Related to Bug #3369: rubyzip 1.0.0 breaks Ruby 1.8 build added
- Related to Bug #3005: gettext 3.0.0 breaks Ruby 1.8 support added
- Related to Bug #3167: gettext_i18n_rails 1.0.0 incompatible with gettext 2.x added
- Related to Bug #2808: nokogiri 1.6.0 incompatible with Ruby 1.8 added
- Related to Bug #2385: Capybara 2.1.0 incompatible with Ruby 1.8 added
- Related to Bug #2100: KS provisioning template regexp buffer overflow added
Debian 6 (squeeze) and Ubuntu 12.04 (precise) both use 1.8.7 as default, but Debian 6 will be EOL soon (May 2014) and 12.04 will be supplanted by 14.04 shortly.
They're able to switch to 1.9.2/3 by default, but both ship Ruby 1.9 versions that aren't supported by Puppet upstream, so doing this can't really be recommended.
It seems that using Debian 7 and Ubuntu 14.04 as our primary versions for these distros would be a good cue to begin dropping 1.8 support (maybe Foreman 1.6 or equivalent).
1.8 support will probably continue for the smart proxy and probably Hammer for longer, since they use the system Ruby 1.8.7 on EL6, rather than software collections.
The proxy has to load Puppet, which remains packaged for 1.8 (though they're talking about dropping support - how isn't clear, yet), while I think we used 1.8 for Hammer to reduce dependencies. Now SCL's released, using it for Hammer on EL6 might well be sensible.
- Related to Bug #4828: Rake 10.2.0 breaks Ruby 1.8 compatibility added
- Related to Bug #5214: Ancestry 2.1.0 dropped Ruby 1.8 support added
- Related to Bug #5966: execjs 2.1.0 drops Ruby 1.8 compatibility added
- Related to Bug #6533: rest-client 1.7.0 dropped Ruby 1.8 support added
- Related to Bug #7013: apipie-rails 0.2.3 is incompatible with 1.8.7 added
- Blocked by Feature #7227: Move Ubuntu 12.04 packages to Brightbox PPA with Ruby 1.9 added
- translation missing: en.field_release set to 21
- Status changed from New to Closed
- Target version set to 1.7.2
- % Done changed from 0 to 100
Also available in: Atom
PDF