[katello-devel] moving to ruby 1.9.3

[Lukas Zapletal]

On Wed, Oct 17, 2012 at 08:46:27AM -0700, Michael McCune wrote:
> On 10/17/2012 08:37 AM, Dmitri Dolguikh wrote:
> >As part of port to Ruby 1.9.3, I'd suggest moving away from custom ruby
> >repository for bundler-based installs, and switch to rubygems.org
> >repository instead. Folks still would rather use Fedora-provided gems
> >can do so, since Fedora 17 versions of 'bundler' and 'gem' are
> >yum-aware. This would simplify dependency management during development.
> 
> this sounds appealing, what is the best way to 'try it out' from a
> fresh install perspective?

I like the idea of getting rid of our gem repo, but lemme ask this. Is
there any way of controlling how folks are updating versions in lock
files?

I mean, we built our gem repo because of "instability" of Gemfile.lock
file. Very often someone commited a version bump of something
incompatible - bang.

I expect this should be much better now since we use review request and
we will discuss every single Gemfile change. But in any case, we should
take care!

> >As the next step I'd like to propose to switch to rails 3.2 (the version
> >of Rails that's going to be shipped with f18) in master (which is what
> >Aeolus folks did).
> >

Why not, but I vote for only upgrading Rails and keeping other libraries
on oldest versions possible. I mean, not doing "bundle update" for all,
but just for Rails and doing this carefully step by step, library after
library. Of course, while keeping versions in our spec files in sync.

ps - But what I do not agree is splitting up into development phase and
packaging phase :-) I sent another reply in the thread. Every single
dev can do the split on his own - making "longer" development cycle in
his own branch and preparing packages just before the git pull request.

LZ

-- 
Later,

 Lukas "lzap" Zapletal
 #katello #systemengine