views:

180

answers:

5

I am a developer who has stepped into the world of Rails very recently. I have learnt Rails 2.3.8 and have now landed into a major project in rails. The question we are facing is this: "Should we use Rails 3.0 for development or the older version?"

Our project has a time frame of 4 to 6 months for its release. Will Rails 3.0 be out of beta and supported by hosting service by then? Or should we stick to current stable versions of rails?

+2  A: 

Rails 3 has hit the RC stage, so it should more or less be stable at this point. I'd expect that it'll go gold well within your timeframe. All other things being equal, I'd probably go with 3.0.

Chris Heald
+3  A: 

Consider staying with 2.x Rails. Not all gems support 3.x and those supporting are in beta. You should also use Passenger/Enterprise rails for more stability and optimizations (for 2.x Rails).

Zepplock
Excellent point. Although I would bet the most commonly used gems are up and running for 3.0.
dr
+1  A: 

I don't think anyone can give a definite release date for Rails 3 even though its Release Candidate now. Regardless, I would go with Rails 3. It's far enough along that stability is not a real concern. Plus doing it now keeps you or somone else from having to do it later.

dr
+2  A: 

Rails 3.0 is working well. The problems I've run in to have been gems and plugins that haven't been updated for rails 3.

Check the gems/plugins you plan to use and see if they're compatible.

Paul Schreiber
+4  A: 

This is a hard question because @Zepplock is right and so is everyone else. It really depends on the gems you'll need. In addition, most of the stuff you'll find on the Internet to help you is also geared to Rails 2.x.

It's a hard problem, but I would say: if you can handle the possible problems of being an early adopter of Rails 3.0, it's worth it moving ahead. What nobody has mentioned are differences to Rails 3.0. It really adds some nice changes on all levels. Just the ability to use JQuery (like he rest of the world) instead of Prototype might make it worth it by itself.

Yar
You point about Rails 3.0 having nice changes is what has driven me to this question. I hope as time goes on most common gems will support Rails 3
Avinasha
I'd go with Rails 2.3.8 and simply follow the Railscasts episodes on upgrading to Rails 3 as time allows on your project. This is a pragmatic solution, you aren't blocked today, and you can treat the upgrade as a developer chore by upgrading gradually on a separate branch. It will take time to perform the upgrade, no problem, frequently rebase or merge your master branch changes onto your upgrade branch. What Yar said above may confuse you, there is nothing preventing you from using jQuery with Rails now, I do with all my projects.
Andy Atkinson