On Tue, Nov 5, 2013 at 3:47 AM, marcin <[email protected]> wrote: > Hi Ken, > I'm sorry we're causing you trouble. Right now we have lots of things to do > to get Gitorious 3 running flawlessly, and keeping focus on 1.8 fixes has > perhaps not been top priority. If there are quick fixes we can do to help you > we're happy to do it, but like we've discussed before, this is going to be > increasingly difficult. Also, ruby 1.8.7 has been EOL-ed > (https://www.ruby-lang.org/en/news/2013/06/30/we-retire-1-8-7/) and Rails 4, > which will most probably be a base for Gitorious 4, requires 1.9+ and > recommends ruby 2.0.
Hi Marcin, I'm at the place where I recognize that 1.8.7 compatibility is entirely a lost cause, so these merge requests were simply to allow us to transition Jenkins over to Ruby 1.9.3. That's what I meant in my earlier email: On Sat, Oct 5, 2013 at 4:24 AM, Ken Dreyer <[email protected]> wrote: > Since Gitorious mainline itself is now more heavily tied to Ruby 1.9 > as a minimum dependency, I've given up on maintaining Ruby 1.8 support > in capillary_rb and libdolt as well. I've removed the Ruby 1.8 > buildslave from capillary_rb in Jenkins, so builds are succeeding > there again. So, as one example, if one of our gems is going to run on the ruby193 buildslave, we need to load the simplecov-rcov gem so Jenkins can read the rcov reports. In summary: I'm not trying to maintain 1.8.7 support any more. I'm just trying to make the gems run smoothly on RHEL 6 with Ruby 1.9.3. - Ken -- -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] --- You received this message because you are subscribed to the Google Groups "Gitorious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
