> On Feb 1, 2019, at 3:17 AM, Phil Edelbrock <[email protected]> wrote: > > >> On Feb 1, 2019, at 12:02 AM, Hasan Diwan <[email protected]> wrote: >> >> To be safe, go through a stepwise upgrade, running and fixing your tests at >> each step. -- H >> >> >> On Thu, 31 Jan 2019 at 23:50, raj kumar <[email protected]> wrote: >> I have a Rails app, made 10 years back in 2009 with following version: >> rails version = 2.0.2 >> ruby version = 1.8.7 >> Database = PostgreSQL >> >> Now what steps I should adopt in order to upgrade it to latest version of >> ruby and rails i.e., >> rails version = 5.2 >> ruby version = 2.6 >> Database = PostgreSQL >> >> As per up-gradation rule >> here(https://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html), I >> need to start up-gradation one by one version gradually like, >> 2.x to 3.x >> 3.x to 4.x >> 4.x to 5.x >> >> My question here is, >> Is there any other way to directly update it from 2.x to 5.x? >> >> Note: I can develop it by scratch but my client not agree on that, they just >> asking for update in existing app not build from scratch in latest version >> of Ruby on Rails. >> >> Kindly provide your thoughts. >> >> Thanks > > Good advise by Hasan. If the project isn't that complex, though, you could > just jump to the latest.. .sometimes rewriting incrementally can be a painful > waste of time just to rewrite again as you go from each increment to the next. > > Latest Ruby should be the least of your problems... you will get huge code > speedups from nothing more than upgrading Ruby. Most of the changes to Ruby > since 1.8/1.9 to 2.6 have been to garbage collection speedups. > > ActiveRecord changes and routes might be your most significant rewrites. > Because we're looking at Rails 6 beta as the current, you could also leapfrog > to that? (depending on your scheduling and policies on using betas) > > Good luck! > > > Phil >
I'll second the idea to rebuild. One of the problems you'll run into is finding authoritative documentation for all the little things you'll need to do to go just from 2.0.2 to 2.3.1 (the last stable 2 branch, IIRC). Then rinse and repeat when you go to 3.0.x etc. That many jumps can easily swamp the amount of time it would take to just rebuild. Walter -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/7CD6F56E-5F92-4475-8657-ABF01598BF6E%40wdstudio.com. For more options, visit https://groups.google.com/d/optout.
