Have you ever delayed a Rails upgrade?
With the release of Rails 5.1, you might be eager to get your Rails app up to date. But you may also be several versions behind. If you’ve ever put off a Rails update, we’d love to hear from you. Did your manager not want to prioritize an update? Was your app fragile or lacking test coverage? Was a key gem causing issues? Tell us your Rails update story and we’ll include a quote and link to your Github/Twitter on our blog!
Comments
When a new Rails version is released, we get excited about the changes. We visit the changelog and see what’s new, how performance is going to boost up and more. But we are way delayed with upgrade.
Now, we try our initial step to upgrade the version. We were on Rails 3.2, so we upgraded to version 3.2.22. Everything works fine and all test suits were green. Now we change the version to 4.2. OOP’s we are in trap. From Rails 3 to Rails 4 there are lots of major changes and lots of gem are now incompatible and almost 45% of specs are RED.
Due to major and backward-incompatible changes in activesupport, activerecord gems
Marshal.dumpbehave awkwardly which was hard to catch by any best written specs and also in development environment. We had to perform ROLLBACK from pre-prod enviroment because things created in Rails3 were not supported by Rails4 and we have to face flood of errors on error tracker.Next, we decided to add seperate instances to handle Rails3 created records and Rails4 by usual ones. Woo! it works but with few glitches. Now we deployed to pre-prod and left for a week to get well tested. Finally, we roll-out to production and we have to face few errors, but we compromised it :(.
Next plan is to upgrade to Rails5.1 in next two months. But again we have to face some challenges with some gems but hopefully can be deal easily because now we have experience on upgrading things.
This is Rails upgrade journey from
Rails 3to4.2.8.Post a comment