Updating a Rails 3.2 app to Rails 4 or wait for Rails 5 -


i update rails 3.2 app rails 5 app when 5 released.

will possible or need go 3.2 -> 4.x -> 5

personally, have had more issues making larger jumps on rails projects smaller, more "incremental" ones. 2.x 4.x jump in one, well, sucked :). however, found rails 3.2 -> 4.2 not bad jump app @ work.

in fact, protected_attributes gem added 4.2 version of our app, did not need worry strong params change in rails 4.2 (this gem lets continue use attr_accessible in models).

over time, changing our many models/controllers utilize newer strong params approach, nice other benefits of 4.x branch (enums in particular have been helpful in our particular app) without having refactor dozens upon dozens of controllers/models strong params.

with said, think ideal approach on features of 4.x (and/or 5.x) , ask whether or not features improve app, code, development experience, etc. if yes, i'd update sooner rather later. if no, i'd wait , upgrade when have appropriate time , break in dev schedule.


Comments

Popular posts from this blog

powershell Start-Process exit code -1073741502 when used with Credential from a windows service environment -

twig - Using Twigbridge in a Laravel 5.1 Package -

c# - LINQ join Entities from HashSet's, Join vs Dictionary vs HashSet performance -