Using rails edge or wait for rails 3

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.
--
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk (AT) googlegroups (DOT) com
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe (AT) googlegroups (DOT) com
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

On Thu, Nov 5, 2009 at 12:24 AM, Rodrigo Alvarez <
rails-mailing-list (AT) andreas-s (DOT) net> wrote:

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

--
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk (AT) googlegroups (DOT) com
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe (AT) googlegroups (DOT) com
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

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

On Thu, Nov 5, 2009 at 4:24 PM, Rodrigo Alvarez <
rails-mailing-list (AT) andreas-s (DOT) net> wrote:

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.
--
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk (AT) googlegroups (DOT) com
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe (AT) googlegroups (DOT) com
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---