How can I make my Ruby on Rails 2.3.4 application "Rails 3-ready"

Question

I'm developing an application with Ruby on Rails that I want to maintain for at least a few years, so I'm concerned about the next version coming up soon.

Going from Rails 1 to Rails 2 was such a big pain that I didn't bother and froze my gems and let the application die, alone, in the dark.

On this project I don't want to do that. First because this new version looks awesome, but also because this application may turn into a real product.

• How can I prepare my application so that it will be upgradable with as little changes as possible.

• How time consuming do you think switching version will be?

• And what about my server? Deployment?

I'm already looking at deprecation notices... what else can I do?

Answer 1

The best thing you could do would be to follow development of Rails 3 via blogs and the Github repository and keep up a copy of your app along with it.

The official Ruby on Rails blog is updated with "What's new in Edge" posts every once in awhile. There are other blogs that often write about new things in edge as well. Larger features are often highlighted in these blogs, so you know about all the cool new features you can play with.

I'm not sure how close Rails 3 is to release (last I heard the core team was talking about a release at RailsConf 2009 in May), but you can always freeze the edge version of Rails into your application and just see what breaks. If you are using git, or another DVCS, you might make a branch specifically for Rails 3 and periodically update Rails to the latest edge code. Just be aware that edge Rails is a moving target so things in your app may break or fix themselves as you are pulling in newer Rails code.

Update: Jeremy McAnally has a ton of info on upgrading from Rails 2 to Rails 3 on his blog. http://omgbloglol.com/