Hi Chris,<div><br></div><div>About a month ago I did an update from 2.4 to Rails 3.1 but without asset pipeline enabled. It was a little bit painful because the unit test coverage was patchy.</div><div><ol><li>The Rails upgrade plugin was useful</li>
<li>I used Git to manage the upgrade</li><li>There are a few Railscasts about it which are helpful and it looked liked using rvm may have helped (i'm using rbenv)</li><li>Make sure your unit test coverage is good!!!</li>
</ol><div>The pain points I encountered</div></div><div><ol><li>The Active Record sytax had changed a lot and there were a lot of scopes and DB calls in the app I upgraded, some where missed by the plugin.</li><li>There was RJS in the app (errh) which caused a few issues but the prototype gem helped a lot with that.</li>
<li>The mailers changed but actually not too much bother</li><li>Some gems did not work and had to be patched or removed</li></ol><div>+1 for ruby 1.9</div></div><div><br></div><div>Hope that helps,</div><div><br></div><div>
Ben</div><div><br></div><div>-- <br>Ben Aldred<div>Director, Tiny Code Factory</div><div><a href="http://tinycodefactory.com/" target="_blank">web</a> | twitter: <a href="http://twitter.com/tinycodefactory" target="_blank">@tinycodefactory</a> | <a href="http://facebook.com/tinycodefactory" target="_blank">facebook</a></div>
</div><br><div class="gmail_quote">On 5 March 2012 15:10, Sidu Ponnappa <span dir="ltr"><<a href="mailto:ckponnappa@gmail.com">ckponnappa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Go all the way, but via 2.3. Basically 2.1.2 => 2.3.latest => 3.2<br>
<div class="im"><br>
> I'm assuming that the upgrade to 2.3.4 should be reasonably straight forward<br>
</div>That depends on how much metaprogramming fun people have had on this<br>
codebase and how many of your plugins made the transition from 2.1 to<br>
2.3.<br>
<div class="im"><br>
> One thing that is looming in the background is that the test coverage is, er, not 100% and that a lot of the code has been written a long time ago by coders who are no longer here.<br>
</div>The last time we did something like this for a client, it took seven<br>
months. Most of this earned us no revenue because we estimated it<br>
would take four weeks (the app had decent coverage) and billing our<br>
client for this kind of miscalculation on our part would have been<br>
unfair. *sigh*<br>
<div class="im"><br>
> Anyone get any words of advice? Is it worth the pain?<br>
</div>Not really. If the app is business critical, you just have to deal<br>
with it. Just remember to set realistic expectations around delivery<br>
timelines (anywhere from 2 weeks to several months :P) and ensure that<br>
there is a development freeze in place on the codebase while the<br>
migration is in progress. Also, don't do both Ruby and Rails at the<br>
same time.<br>
<br>
Best,<br>
Sidu Ponnappa.<br>
<a href="http://c42.in" target="_blank">http://c42.in</a><br>
<a href="http://rubymonk.com" target="_blank">http://rubymonk.com</a><br>
<a href="http://twitter.com/ponnappa" target="_blank">http://twitter.com/ponnappa</a><br>
<div class="HOEnZb"><div class="h5"><br>
<br>
On 5 March 2012 20:22, Chris Waters <<a href="mailto:chris@yougroup.co.uk">chris@yougroup.co.uk</a>> wrote:<br>
> Hi LRUG,<br>
><br>
> I've got a pretty large application (200ish model classes, 100ish<br>
> controllers) that's been running happily(ish) for about 4 years now.<br>
><br>
> It is Rails 2.1.2 running against Ruby 1.8.7. It feels as though it is time<br>
> that we brought things up-to-date as things are starting to creak.<br>
><br>
><br>
> To my mind, there are 2 options;<br>
> * we upgrade to v2.3.4 and be happy with that for now<br>
> * or continue on from 2.3.4 and go the whole hog and get to v3.2<br>
><br>
> One thing that is looming in the background is that the test coverage is,<br>
> er, not 100% and that a lot of the code has been written a long time ago by<br>
> coders who are no longer here.<br>
><br>
> I'm assuming that the upgrade to 2.3.4 should be reasonably straight<br>
> forward, and that the big leap to 3.2 is likely to hurt more.<br>
><br>
><br>
> Anyone get any words of advice? Is it worth the pain? How many people out<br>
> there are still running against 2.1.2?<br>
><br>
><br>
> Thanks for any comments/help<br>
><br>
> Chris.<br>
><br>
><br>
> Chris Waters<br>
> Lead Developer<br>
> YOU Group<br>
> _______________________________________________<br>
> Chat mailing list<br>
> <a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
> <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
_______________________________________________<br>
Chat mailing list<br>
<a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
<a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
</div></div></blockquote></div><br>