# Moving to Rails 2.x **URL:** \ **Category:** Rails\ **Created:** [September 26, 2008, 1:55am UTC](https://www.ruby-forum.com/t/moving-to-rails-2-x/149545 "2008-09-26T01:55:30Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![lunaclaire](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/f4b2a3/32.png) [@lunaclaire](https://www.ruby-forum.com/u/lunaclaire)\ **Post date:** [September 26, 2008, 1:55am UTC](https://www.ruby-forum.com/t/moving-to-rails-2-x/149545/1 "2008-09-26T01:55:30Z")
Finally about to make the move from 1.2.6 to 2.? and am curious about strategy… I’ve looked at a bunch of postings across the web about upgrading, but many of them seem to be written back when 2.0 was only a RC and it seems like this has been a changing picture throughout the year (one of the reasons I’ve waited). Many of the postings in this group from earlier in the year seem to point to lots of problems in making the move as well and, so, I ask some questions: 1. which version rails is the one to move to (most stable and ready)? 2. when I update does the process leave old gems in place so that if I need to move back, it’s “easy”? 3. if I want to try starting a new small app to learn the ropes vs. updating my big app, can I leave all the rails 1.2.6-oriented pieces in place and just set RAILS\_GEM\_VERSION to the 2.x version I’ll be using? or is it messier in some way? I’m sure there’s more I could be asking here and I’d be glad for this to start a thread discussing/revealing any issues and gotchas to watch out for. As you can see from my questions, I’m mostly trying to avoid really messing things up before I start. ---
**Author:** ![lunaclaire](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/f4b2a3/32.png) [@lunaclaire](https://www.ruby-forum.com/u/lunaclaire)\ **Post date:** [September 26, 2008, 9:18am UTC](https://www.ruby-forum.com/t/moving-to-rails-2-x/149545/2 "2008-09-26T09:18:36Z")
On Sep 26, 12:54 am, lunaclaire [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > some questions: > > 1. which version rails is the one to move to (most stable and ready)? I would go straight to the latest stable (ie 2.1.1). The one caveat to that is that it could be the case that some things were marked as deprecated in 2.0 and then removed in 2.1. If you moved to 2.0 first then you get the deprecation warnings rather than have stuff just disappear. I doubt much stuff like that is out there though. > 1. when I update does the process leave old gems in place so that if I > need to move back, it’s “easy”? Yes > 1. if I want to try starting a new small app to learn the ropes vs. > updating my big app, can I leave all the rails 1.2.6-oriented pieces > in place and just set RAILS\_GEM\_VERSION to the 2.x version I’ll be > using? or is it messier in some way? Yes, you can quite easily have some 1.2.x apps and some 2.x apps Fred ---
**Author:** ![lunaclaire](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/f4b2a3/32.png) [@lunaclaire](https://www.ruby-forum.com/u/lunaclaire)\ **Post date:** [September 26, 2008, 10:37am UTC](https://www.ruby-forum.com/t/moving-to-rails-2-x/149545/3 "2008-09-26T10:37:11Z")
X-No-Archive: yes Hi, this article helped me when updating: [http://blog.insoshi.com/2008/07/03/a-rails-21-case-study-upgrading-the-insoshi-social-networking-platform/](http://blog.insoshi.com/2008/07/03/a-rails-21-case-study-upgrading-the-insoshi-social-networking-platform/) Cheers On 26 Sep., 09:18, Frederick C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) ---
**Author:** ![lunaclaire](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/f4b2a3/32.png) [@lunaclaire](https://www.ruby-forum.com/u/lunaclaire)\ **Post date:** [September 30, 2008, 8:24pm UTC](https://www.ruby-forum.com/t/moving-to-rails-2-x/149545/4 "2008-09-30T20:24:37Z")
thanks, guys… very helpful… into the breach! On Sep 26, 1:36 am, “berlin 2.0” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)