ATLRUG - Upgrading Rails (Isn't So Bad)

ATLRUG - Upgrading Rails (Isn't So Bad)

Full-length version of my lightning talk from Rails Girls 6/29/16. Given on 7/13/16 at the Atlanta Ruby Users Group.

Upgrading Rails gets a bad rap, but it doesn't have to be so daunting if we listen to our tools and remember that we're in control.

817f5f1ada5fdeffcd14668107c08f0a?s=128

Megan Tiu

July 13, 2016
Tweet

Transcript

  1. 7.

    When should I upgrade? • The larger your app, the

    later you should wait ◦ Bug fix patches will follow shortly ◦ Not all dependencies will be ready for Rails 5 • Smaller apps with few dependencies will likely be ready
  2. 12.

    1. Start with a clean test suite • No deprecation

    warnings • All tests passing • As many gems up-to-date as possible
  3. 13.
  4. 18.
  5. 20.
  6. 25.
  7. 26.
  8. 30.
  9. 31.
  10. 34.
  11. 39.
  12. 40.

    Takeaways and tips: • Break dependency upgrades into chunks •

    Read your gems’ changelogs • Look up your deprecation warnings • Error messages are your friend • You are in control