On 07/21/11 - 10:34:34AM, Hugh Brock wrote:
On Thu, Jul 21, 2011 at 10:20:56AM -0400, Chris Lalancette wrote:
> All,
> A group of us are working on updating the conductor codebase. Not only
> will this move us onto the new hotness of Rails 3, it will also make it so that
> we can get Aeolus into Fedora.
>
> What does this mean for you? Since Rails 2 and Rails 3 are incompatible, it
> means that we are going to have to have a "flag day" where we push the
Rails 3
> code to master, and everyone will have to switch over. Now that we have
> branched off for 0.3.0, we can do this at any time. Note, however, that the
> only place we have the RPM dependency situation completely (or mostly) sorted
> is in Fedora rawhide. Fedora 14, Fedora 15, and RHEL-6 have not yet been
> evaluated for packages.
>
> My suggestion is to merge the rails 3 code into master sooner rather than
> later. That way, we can get the whole team to help in flushing out the Rails 3
> bugs, and it will go much faster that way. What do people think about this
> approach? In the very short-term it may stall development as we get it back
> up and running, but I think it will lead to a much shorter recovery time.
Do we really want to force the whole dev team onto Rawhide until we
get f15 packaging sorted out? Or is that not what you're suggesting?
That's not exactly what I'm suggesting, though I see how it could seem that
way :). Despite my aversion to gems, what I'm actually suggesting is that
people either:
a) Use rawhide
b) Use gems, instead of RPMs, to satisfy the dependencies, on the platform
of their choice
Again, this is only a short-term thing; once we have more stable and working
code, we'll get the packages built for the other platforms (and rawhide will
get more stable), so we can then switch back to RPMs only.
--
Chris Lalancette