-
Notifications
You must be signed in to change notification settings - Fork 58
Upgrade to Rails 4.1 #585
Comments
will update as work continues |
Great! Don't forget to remove Spork as well since we're switching to Spring. |
Can't figure this one out :( Every spec in the models/ passes, thankfully
|
Okay, I got distracted by bootstrap but I decided to set it aside for another branch since it's way too big of a project to incorporate into the rails 4 PR. The site finally renders with very few display issues and there are only 86 failing tests left to look at. more notes
|
Good call, let's try and keep our PR's as focused as possible. Given how many dependencies we might be stressing, I would recommend getting the big Rails 4 upgrade done first so that we can base all of the other work on that foundation rather than potentially uncover / create more dependency issues. Great work though! |
0 failures on development locally, though some still fail on travis (grr) |
Amazing! Give Travis an hour or two to catch up :-P |
With 19 security risks according to Gemnasium, updating to the newest stable version of Rails (4.1) seems imperative. While absent in client negotiations, this should be a top priority after 3.3.0.
The good news is that by all counts, the process is not nearly as strenuous as the Rails 2 -> Rails 3 update.
Resources
Preparation
Ruby >= 1.9.3
Upgrade to Rails 4 is possible on our current Ruby version; after #535 is merged into development, we should be golden.
Testing coverage
All guides concur that testing coverage should be as complete as possible. This means that #403, #404, #416 and #577 should be prerequisites for the upgrade.
Gems
According to [http://www.ready4rails4.net/gemfile_check/new], only CanCan is definitely not ready for Rails 4 (as of 4 months ago); the status of rdoc, rubycas-client-rails, net-ldap, permanent_records, jquery_datepicker, spinjs-rails, fuubar, yajl-ruby, pry-stack_explorer, pry-remote, and letter_opener_web is unknown to the site. That said, CanCan has been continued as CanCanCan and should be backwards-compatible; also, the latest CanCan version reportedly works if StrongParameters are not used and the protected_attributes gem is installed (which is what we should do at the start, anyway).
Tools
Relevant Changes / Deprecations
Relevant as in "Reservations uses some of the features that are newly deprecated".
Relevant and action required
attr_*
extracted into the (protected_attributes gem)[https://github.com/rails/protected_attributes]; the suggested default now is Strong Parameters, although the two reportedly don't mix well.match
with unspecifiedvia:
is no longer supported. We have at least four such routes.Relevant and won't affect us
.update_attributes
->.update
Relevant for the future
.includes(:resource)
will be useful to know for addressing speed concerns / N+1 queries in Speed-testing #574.:controller/(de)?activate
will now be able to be refactored into a route concernUnaddressed in this post
The text was updated successfully, but these errors were encountered: