These new releases of Ruby address a security issue (CVE-2015-7551). If you’re new to Ruby, check out this online course from The Pragmatic Studio to learn all the fundamentals of object-oriented programming with Ruby.
You can find the links to those archives in the download section.
Certain members in the Ruby community feel very strongly that you should never use a package manager to install Ruby and that you should use tools instead.
In this article, I’ll try to cover all the issues that I had, when I was upgrading one of my Rails app from Ruby on Rails 4.2 to Ruby on Rails 5.0.
Note: This is not a complete, covering every possible case tutorial. If so, feel free to comment and I will try to update the post with other issues and solutions. If you don’t have a good code coverage level and you lack tests, upgrading from Rails 4.2 to Rails 5 might be a big problem.
This gem brings back assigns to your controller tests as well as assert_template to both controller and integration tests.
If you use those methods, after upgrading to Ruby on Rails 5, you will have to add it.