Skip to content

Instantly share code, notes, and snippets.

@truffaut
Last active August 29, 2015 14:25
Show Gist options
  • Save truffaut/84c92d67c739e544e231 to your computer and use it in GitHub Desktop.
Save truffaut/84c92d67c739e544e231 to your computer and use it in GitHub Desktop.

It's time to start talking about upgrading to Rails 4. The sensible path seems to be 3.2 -> 4.0 -> 4.1 -> 4.2, fixing issues and deprecations along the way.

A few links for more information about what will need to change as we move to Rails 4:

We'll also need to probably do an audit of our gems, since some of them have no Rails 4 compliant version.

Features we are definitely using that are deprecated (non-exhaustive list):

  • attr_accessible, replaced by strong_parameters
  • Observers replaced by nothing explicitly, but we can use callbacks or refactor to replace these
  • occasional deprecated dynamic finders (things like find_all_by_...)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment