Greetings, I'm currently looking into updating some rubygems in EPEL to the latest upstream release to address some security issues.

Additionally as outlined below I'd like to start driving towards updating Rails in EPEL to the latest release (4.2.1).

I was looking for thoughts / opinions as to how to best proceed with this so as maintain the right balance between stability & progress.

I was currently thinking about pushing the rails update to EL7 and possibly EL6 though it may be best to leave the older releases as is.

Since gems are fairly dynamic in general, I'm also ooking to pushing the updates to the smaller gems (incorporating the security fixes) to all three EPEL branches. Are there any objections to this?

Of course help with any of this would be appreciated, there are quite a few packages that will need updated.

  -Mo

[1] https://bugzilla.redhat.com/show_bug.cgi?id=917234
[2] https://bugzilla.redhat.com/show_bug.cgi?id=917237


-------- Forwarded Message --------
Subject: updating rails in epel to 4.x
Date: Fri, 12 Jun 2015 10:28:12 -0400
From: Mo Morsi <mmorsi@redhat.com>
Reply-To: Ruby SIG mailing list <ruby-sig@lists.fedoraproject.org>
To: ruby-sig@lists.fedoraproject.org 


I've done some investigation as to updating rails in EPEL to the latest 
release (4.2.1).

As part of this I've been refactoring polisher [1] and have written a 
few new utilities to cross reference upstream / downstream dependencies 
and output the results in in a tree like manner [2][3] as well as to 
highlight upstream dependencies missing downstream [4].

The results of the last utility run [5] should give a rough estimate of 
the work entailed. Dev deps have been included for this run so many 
updates are duplicate / unecessary.

I'll look into consolidating this list and taking some of the simpler 
updates in the near future, obviously the more eyeballs that we get on 
this, the quicker it will go.

   -Mo

[1] https://github.com/ManageIQ/polisher
[2] https://github.com/ManageIQ/polisher/blob/master/bin/gem_mapper.rb
[3] https://mmorsi.fedorapeople.org/gem_mapper.png
[4] https://github.com/ManageIQ/polisher/blob/master/bin/missing_deps.rb
[5] https://mmorsi.fedorapeople.org/missing_deps_output
_______________________________________________
ruby-sig mailing list
ruby-sig@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig