Ruby on Rails Monday, May 2, 2011

On 2 May 2011 10:06, Hans <Hans.Marmolin@klockholm.se> wrote:
> I have a rather large application in rails 2.3.6 (about 40 controllers
> and 20 plugins) with a working version in 2.3.11
> I am planing to upgrade to rails 3 and at the same time upgrading to
> html5, css3 and to jquery
>
> My question is the following
>
> Should I try to upgrade the existing application as described in e.g
> the book Raisl 3 upgrade handbook, rafactoring all of it ??
>
> Or should I Generate a new Rails 3 application copying the code action
> for action method for method from the old application at the same time
> as I am refactoring the copied parts ???
>
> Any-one that had the same problem ?
> Any experiencies of these approaches ?
> Which one should I use, considering that I have not implemented any
> tests ? (Will do that at the same time)
>

First I assume you are using a source control system (git for
example). If not then start with that.
Then I suggest writing tests before making any changes, otherwise you
will not be confident all is working. Then upgrade to rails 3 only
changing what needs to be changed to make it work (ie passing tests).
Then proceed with enhancements and re-factoring.

Colin

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

No comments:

Post a Comment