Skip to content

Instantly share code, notes, and snippets.

@AlfonsoUceda

AlfonsoUceda/rails4.md

Last active November 18, 2016 07:35
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save AlfonsoUceda/0609c89f549fc2cbed7bf5db2a3f7cba to your computer and use it in GitHub Desktop.
Save AlfonsoUceda/0609c89f549fc2cbed7bf5db2a3f7cba to your computer and use it in GitHub Desktop.
Download ZIP
Rails 4 here we go!
Raw
rails4.md

Rails 4 here we go!

Why we need Rails 4? Why is it nicer? No! well it is but that isn't the key. Our two main reasons are security and performance. I've been researching our current situation to migrate Rails 3.2 to Rails 4.0.13 and Paco has been done a lot of things.

He created two branches paco/rails4-compat and paco/rail4, the first one is a branch with changes needed in rails 4 but they are compatibles with rails 3 to make easier the upgrade, the latter has the minimum changes needed to upgrade to rails 4.

One solution to upgrade rails 4, it could be deploy to master when everything is fine in local and test passing, I mean, check in production mode in localhost and test the main points of the application.

I've created two PRs for both branches, first we need to merge paco/rails4-compat in master (and stable) and finally merge paco/rails4 in master and leave there one week or so. I explain in those PRs how should be updated because they are sync with stable so there aren't problems related to conflicts.

@davilious
Copy link

davilious commented Nov 18, 2016 •
edited

Exciting. Will be able to use Sass 3 with this version of Rails and all upgrades you guys are doing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment