# New Project \> Rails 2 or 3?

**URL:** <https://www.ruby-forum.com/t/new-project-rails-2-or-3/189326>\
**Category:** Rails\
**Created:** [May 28, 2010, 7:55pm UTC](https://www.ruby-forum.com/t/new-project-rails-2-or-3/189326 "2010-05-28T19:55:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![brianp](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/94ad74/32.png) [@brianp](https://www.ruby-forum.com/u/brianp)\
**Post date:** [May 28, 2010, 7:55pm UTC](https://www.ruby-forum.com/t/new-project-rails-2-or-3/189326/1 "2010-05-28T19:55:39Z")

</div>

Hey,

Working on a project for a new startup. We started it in Rails 2.3.5.  
but now the project manager is talking about wanting to switch to  
Rails 3 because it’s the hot new thing.

Whats the consensus if rails is ready for production environments that  
the customers will depend on? I haven’t looked into it to much yet  
figured i’d start here.

Cheers,  
bp

---

<div class="post-metadata">

**Author:** ![brianp](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/94ad74/32.png) [@brianp](https://www.ruby-forum.com/u/brianp)\
**Post date:** [May 28, 2010, 10:32pm UTC](https://www.ruby-forum.com/t/new-project-rails-2-or-3/189326/2 "2010-05-28T22:32:43Z")

</div>

brianp wrote:

> Working on a project for a new startup. We started it in Rails 2.3.5.  
> but now the project manager is talking about wanting to switch to  
> Rails 3 because it’s the hot new thing.
> 
> Whats the consensus if rails is ready for production environments that  
> the customers will depend on? I haven’t looked into it to much yet  
> figured i’d start here.

I would say that step one would be to update your application (on a  
branch) to Rails 2.3.8. After doing that install the rails\_xss gem  
([GitHub - rails/rails\_xss: A plugin for rails 2.3 apps which switches the default to escape by default](http://github.com/rails/rails_xss#readme)). Once that’s complete then  
fix all deprecation warnings.

At this point, assuming everything is working correctly, I’d call this  
my “stable” version of the application. Now it’s time to create a Rails  
3.0 branch and start updating your application to use some of the new  
syntax and router capabilities. Once you have a working Rails 3.0  
application that you’re happy with then you will have a much better idea  
whether you’re ready to trust your application running under Rails 3.0.

If you have the capability of doing so, roll out a beta of your site to  
your customer and ask them for feedback and bug reports. If all that  
goes smoothly then you might feel comfortable putting that into  
production. I’d still leave the beta status on the site until we have an  
official release of Rails 3.0 though.