mccannf
mccannf

Reputation: 16659

Easing the pain of transition to Rails 4

I am working on a Rails 3.2 application now, but I am aware that Rails 4 is just around the corner. What are the things I should be aware of now when implementing my application to make it easier to migrate to Rails 4 when it is formally released or perhaps after the couple of point releases? I know that some of the functionality will be spun out into gems, but then there is no guarantee of support in Rails 4.1+.

I have read the upgrade guide: http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-3-2-to-rails-4-0, and the release notes: http://edgeguides.rubyonrails.org/4_0_release_notes.html.

I am more interested in this point to identify the gotchas that would cause me headaches in an upgrade, rather than the nice new shiny features of Rails 4.

So based on this reading and snippets from the Internet, what I have at the moment is:

...but I'm sure there is more. Could anyone provide a comprehensive but common-sense list to be aware of? I'm not looking for a full list of deprecations in Rails 4 - it's the big things to be aware of and what I can do now to future-proof for them.

Upvotes: 6

Views: 2100

Answers (0)

Related Questions