Ruby 1.9.3 EOL

Development
1

Bug fixes end today

https://www.ruby-lang.org/en/news/2014/01/10/ruby-1-9-3-will-end-on-2015/

Is there a way to build against CentOS 7 2.0 or a newer ruby for all the
SCL stuff tied into foreman?

2

On EL7 we're tied into SCLs, which I mostly did because they also
provide Ruby on Rails packages and it made it easier to port from EL6.
(Using SCLs means we get a lot of consistency.)

There's been some work on Rails 4 support lately, which means we'll be
able to move to a newer software collection when it's available.
Currently there's a Rails 4.0 on Ruby 2.0 collection, but since Rails
4.0 is also EOL, we're holding off a little to move to 4.2 + 2.1.
Hopefully in the next release cycle!

··· On 24/02/15 14:28, Byron Miller wrote: > Bug fixes end today > > https://www.ruby-lang.org/en/news/2014/01/10/ruby-1-9-3-will-end-on-2015/ > > Is there a way to build against CentOS 7 2.0 or a newer ruby for all the > SCL stuff tied into foreman?

–
Dominic Cleal
Red Hat Engineering

3

Correction, RoR 4.2 and Ruby 2.2.

··· On 24/02/15 14:42, Dominic Cleal wrote: > There's been some work on Rails 4 support lately, which means we'll be > able to move to a newer software collection when it's available. > Currently there's a Rails 4.0 on Ruby 2.0 collection, but since Rails > 4.0 is also EOL, we're holding off a little to move to 4.2 + 2.1. > Hopefully in the next release cycle!

–
Dominic Cleal
Red Hat Engineering

4

> On EL7 we're tied into SCLs, which I mostly did because they also
> provide Ruby on Rails packages and it made it easier to port from EL6.
> (Using SCLs means we get a lot of consistency.)
>
> There's been some work on Rails 4 support lately, which means we'll be
> able to move to a newer software collection when it's available.
> Currently there's a Rails 4.0 on Ruby 2.0 collection, but since Rails
> 4.0 is also EOL, we're holding off a little to move to 4.2 + 2.1.
> Hopefully in the next release cycle!

Just to complement the information - we base off official Red Hat
Software Collections, therefore upstream EOL is not that relevant here.
The RHSCL support pace is two years, therefore ruby193 collection (v1)
has EOL Sep 30, 2016. We have some extra time to set things up.

Currently we must rebuild security patches ourselves into our
collection, but there are upcoming changes AFAIK which will allow us to
use RHSCL repositories directly bringing patches faster and with less
effort.

··· -- Later, Lukas #lzap Zapletal
5

sweet! thanks for the update

··· On Tuesday, February 24, 2015 at 9:09:42 AM UTC-6, Dominic Cleal wrote: > > On 24/02/15 14:42, Dominic Cleal wrote: > > There's been some work on Rails 4 support lately, which means we'll be > > able to move to a newer software collection when it's available. > > Currently there's a Rails 4.0 on Ruby 2.0 collection, but since Rails > > 4.0 is also EOL, we're holding off a little to move to 4.2 + 2.1. > > Hopefully in the next release cycle! > > Correction, RoR 4.2 and Ruby 2.2. > > -- > Dominic Cleal > Red Hat Engineering >
6

What do you mean? We support using softwarecollections.org, CentOS SCL
(on EL6) and RHSCL builds of the RHSCL collections, we don't ship them
ourselves.

We only fix issues in the additional packages we hold.

··· On 25/02/15 08:29, Lukas Zapletal wrote: > Currently we must rebuild security patches ourselves into our > collection, but there are upcoming changes AFAIK which will allow us to > use RHSCL repositories directly bringing patches faster and with less > effort.

–
Dominic Cleal
Red Hat Engineering

7

> We only fix issues in the additional packages we hold.

You are right, I was under impression we ship newer version of Rails or
something.

··· -- Later, Lukas #lzap Zapletal
8

Yeah, not right now and it's a source of frustration for some due to
missing features or lingering bugs, but a weight off of the backs of me
& others in terms of maintenance work.

What I think may help with these frustrations is the work in the CentOS
SCL SIG community which is planning to become an upstream for RHSCL,
both supporting the current collections and to develop new ones. (The
start of
https://www.redhat.com/archives/sclorg/2015-February/msg00023.html
expands slightly on this.)

I've been watching from the sidelines a little, but I'm quite keen to
contribute to collections in the SIG once it's running so we see
collections and bugs fixes coming through that solve the problems we
have. I don't quite know what it will look like yet - perhaps we will
have nightlies working against the latest SIG collections and then base
our releases on their stable releases, or even wait for them to reach
RHSCL stable releases.

Either way, this looks to be the future of development for the
collections we use, and I think it will allow us in due course to keep
Foreman running on the latest technologies instead of sticking to Rails
3.2 etc.

··· On 25/02/15 09:35, Lukas Zapletal wrote: >> We only fix issues in the additional packages we hold. > > You are right, I was under impression we ship newer version of Rails or > something.

–
Dominic Cleal
Red Hat Engineering

9

A key point I forgot is that other users and projects are interested and
involved in the SIG, so it will allow us to continue to share the
workload for common components like Rails. I hope we can also find
packages that we maintain ourselves that we can move into shared
collections in the future.

··· On 25/02/15 11:13, Dominic Cleal wrote: > On 25/02/15 09:35, Lukas Zapletal wrote: >>> We only fix issues in the additional packages we hold. >> >> You are right, I was under impression we ship newer version of Rails or >> something. > > Yeah, not right now and it's a source of frustration for some due to > missing features or lingering bugs, but a weight off of the backs of me > & others in terms of maintenance work. > > What I think may help with these frustrations is the work in the CentOS > SCL SIG community which is planning to become an upstream for RHSCL, > both supporting the current collections and to develop new ones. (The > start of > https://www.redhat.com/archives/sclorg/2015-February/msg00023.html > expands slightly on this.) > > I've been watching from the sidelines a little, but I'm quite keen to > contribute to collections in the SIG once it's running so we see > collections and bugs fixes coming through that solve the problems we > have.

–
Dominic Cleal
Red Hat Engineering