Paul Jonathan Thompson
2010-Apr-13 22:22 UTC
Advise sought: Upgrade from Rails 2.0.1 to current
I have upgraded from 1.2.6 to 2.0.1 and successfully passed all my test and manual testing. Everything seems to be working correctly. My application is pretty vanilla and so there where few complications. Question is, should I do another point upgrade (and if so, which point to upgrade to next) or is it safe (and prudent) to just go straight on to the current version (2.3.x). Advise would be most welcome. Paul Thompson -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Rick DeNatale
2010-Apr-15 16:44 UTC
Re: Advise sought: Upgrade from Rails 2.0.1 to current
I would advise stepping first to 2.1 since there were a lot of changes to ActiveRecord with that release (partial updates/dirty attribute tracking) which had subtle effects on things like callbacks. For some of the apps I was involved in, 2.0 -> 2.1 was actually a more difficult transition than 1.2.x -> 2.0. On Tue, Apr 13, 2010 at 6:22 PM, Paul Jonathan Thompson <rails001-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> I have upgraded from 1.2.6 to 2.0.1 and successfully passed all my > test and manual testing. Everything seems to be working correctly. My > application is pretty vanilla and so there where few complications. > Question is, should I do another point upgrade (and if so, which > point to upgrade to next) or is it safe (and prudent) to just go > straight on to the current version (2.3.x). > Advise would be most welcome. > > Paul Thompson > > -- > 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > 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. > >-- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Github: http://github.com/rubyredrick Twitter: @RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn: http://www.linkedin.com/in/rickdenatale -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 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.
Paul Jonathan Thompson
2010-Apr-15 20:34 UTC
Re: Advise sought: Upgrade from Rails 2.0.1 to current
Rick, Thanks for that. I have done just done that and have gone on to 2.3.5 and now am trying to get Rails 3 beta 3 working, So far it has not been to bad for me, mostly just a process of fixing redundancies as my code is very vanilla and no plugins. So far, Rails 3 is shaping up to be the most difficult one (I have gone from 1.2.2 - 1.2.6 - 2.0.1 - 2.1 - 2.3.5 now 3 beta3 in the last two weeks). Regards, Paul Thompson On 16 April 2010 04:44, Rick DeNatale <rick.denatale-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> I would advise stepping first to 2.1 since there were a lot of changes > to ActiveRecord with that release (partial updates/dirty attribute > tracking) which had subtle effects on things like callbacks. For some > of the apps I was involved in, 2.0 -> 2.1 was actually a more > difficult transition than 1.2.x -> 2.0. > > On Tue, Apr 13, 2010 at 6:22 PM, Paul Jonathan Thompson > <rails001-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: >> I have upgraded from 1.2.6 to 2.0.1 and successfully passed all my >> test and manual testing. Everything seems to be working correctly. My >> application is pretty vanilla and so there where few complications. >> Question is, should I do another point upgrade (and if so, which >> point to upgrade to next) or is it safe (and prudent) to just go >> straight on to the current version (2.3.x). >> Advise would be most welcome. >> >> Paul Thompson >> >> -- >> 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org >> To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org >> For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.-- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 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.