Using rails edge or wait for rails 3

rubyonrails-talk
1

Hi all,

I'm developing a CMS prototype and I plan to use rails 3. The thing is, do I need to change anything important in my rails 2 application to support rails 3 features? Like in environment, initializers or any "core" file, or I can just freeze rails edge in vendor and I get the same stuff as if I had generated the application with rails edge command?

thanks in advance.

2

Hi all,

I’m developing a CMS prototype and I plan to use rails 3. The thing is,

do I need to change anything important in my rails 2 application to

support rails 3 features? Like in environment, initializers or any

“core” file, or I can just freeze rails edge in vendor and I get the

same stuff as if I had generated the application with rails edge

command?

thanks in advance.

Rodrigo, It’s really hard to say whether your will or will not work on Rails 3.0.

Thus, I would recommend that you check your Rails 3.0 compatibility by testing

your app against Edge. You might want to keep up to date with the

threads/blogs in regards to Rails 3.0:

http://yehudakatz.com/tags/rails-3/

http://drnicwilliams.com/2009/11/03/first-look-at-rails-3-0-pre/

http://ryandaigle.com/

Lastly, Rails 3.0 will require Ruby 1.8.7 and prefer Ruby 1.9.2.

Good luck,

-Conrad

3

Hi Rodrigo,

We’re in the same situation as you. After some hard working with rails 3 we just come back to rails 2.3. IMHO, rails 2.3 provides much more better experience than rails 3: all plugins work instantly.

If you’d like to try rails 3, prepare to roll your own rspec/cucumber generator and common module like authentication.

Best, Jan