rails 3.0.x in F15

[Mohammed Morsi]

  On 12/18/2010 02:12 AM, Mamoru Tasaka wrote:
> Hello, Mohammed:
>
> First of all, thank you for analyzing what to be done for rails 3.0.

No problem. Appreciate your feedback / comments.

> Mohammed Morsi wrote, at 12/18/2010 10:48 AM +9:00:
>>     Based on my discussions with the community and various parties that
>> have a vested interest in this, I feel that it is a good idea to move
>> the rubygem-rails packages to rails 3.0.x for F15 so that we don't get
>> left behind and stay up to date w/ the latest / greatest upstream releases.
>>
>> Unfortunately this process isn't as simple as updating the 6 rails
>> packages (rails itself and the active/action* packages), there are many
>> various gems which will need to be updated as well to work with Rails 3.
>> Based on my findings w/ deltacloud [1], the update process itself isn't
>> so difficult, but some of the following gems will need to be updated in
>> Fedora for things to properly work. Most likely more will need to be as
>> well, these are just the ones that I've found, but conversely all of
>> these may not need to be updated, as I installed Rails 3 via gem which
>> pulled in the latest version of all these packages.
>>
>> * rails, activesupport, activerecord, actionpack, activeresource, actionmailer   -  2.3.8 ->    3.0.1   (mmorsi)
>> * compass                 -  0.8.17  ->    0.10.6 (mmorsi)
>> * cucumber  -  0.9.0    ->    0.9.3   (kanarip, mfojtik, mkent, stahnma)
>> * erubis        -  2.6.5    ->    2.6.6  (mkent)
>> * gherkin      -  2.2.4    ->    2.2.9   (mfojtik)
>> * haml          -  3.0.17  ->    3.0.23  (mkent, kanarip)
>> * polyglot     -  0.2.5    ->    0.3.1   (kanarip, stahnma)
>> * rack           -  1.1.0    ->    1.2.1 (kanarip, stahnma)
>> * rack-test   -  0.5.4    ->     0.5.6   (mfojtik)
>> * rspec         -  1.3.0    ->    2.0.1  (stahnma)
> - rspec 1.3.0 and rspec 2.0.1 have large difference, and it seems that
>     many packages depends on rspec 1.3.0 (I may be wrong). So maybe we want
>     to package rspec 2.0.1 as rubygem-rspec-2 (correct me if I am wrong).
>     Also please check bug650283
>

I would be fine w/ this, but would like to make sure it needs to be done 
before we create a new package as doing so involves more work. Perhaps 
instead we can convince the maintainers of the dependent gems to update 
their packages

> <snip>

Thanks for the rest of your feedback, going over it, it seems that 
updating to Rails 3.0.x seems doable, even if it involves a bit of work. 
At least it doesn't seem like there won't be any major blockers as we 
get this ball rolling (famous last words, might find some when we 
actually do this). In the upcoming days/weeks look for update requests 
in bugzilla as well as preliminary Rails 3 packages here.

   -Mo