-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to Rails 6.x (was 4.2, but now we're aiming higher). #126
Comments
After reviewing this a bit more, it would definitely be a more challenging upgrade. Custom database serialization changed significantly between Rails 4.1 and 4.2, and it's relied heavily by |
Note that Rails 4.2 is no longer supported. Upgrading to Rails 4.2 may still be a useful stepping stone to upgrading to a supported version, though! |
The latest stable Rails release is 6.0.2.2 (of 19 March 2020), FWIW. |
Upgrade Active Admin to 2.7. |
This shouldn't actually have been closed because we are continuing on with rails 5 upgrade! |
This was breaking twilio photo uploads (at least in dev). Issue #126: Upgrade to Rails 6.x
Issue #126: Upgrade to Rails 6.x
Three issues were found: * Shift Territory Shifts was awkward language (from County Shifts) * A small UI update requested while in there (swapping columns in data scheduler) * Bootstrap update caused some form alignment issues Issue #185: Change entity names
Issue #126: Upgrade to Rails 6.x (was 4.2, but now we're aiming higher)
Issue #126: Upgrade to Rails 6.x (was 4.2, but now we're aiming higher)
We're looking at upgrading to the highest version of Rails 4.1 in #119, but when possible we should try to upgrade to Rails 4.2. This may be challenging because of the use of a deprecated form column serialization in
arcdata_core
that we're still looking into.The text was updated successfully, but these errors were encountered: