"It depends" variables:
* how much time do you have?
* how many people are working on it?
* are features being added while you're trying to upgrade?
* has anyone there done a significant upgrade?
* how complete is your test suite?
Just based on what you've said so far, I'd still recommend doing the
short trip to 188.8.131.52 as practice. Then go to 4.0.x and if you're feeling
confident jump to 5.0.x.
Doing essentially a rewrite by moving stuff into a bare Rails 5 app
is a valid approach too, but again, it depends.
There is really no scenario where you don't still have to sort out the
changed gem dependencies and rewrite a bunch of code, though.
On Fri, Mar 6, 2020 at 1:15 PM Jack Royal-Gordon <firstname.lastname@example.org> wrote:
I get it, but where I stand is that the app is stable on 3.2.21, and I need to upgrade it to a more recent (supported) version of Rails. I got some advice that indicated that I should move up minor version by minor version, and that the first step would be to move to 184.108.40.206 (last stable version of 3.2) before moving up from there. Under the circumstances, since that’s not going so well, might it make sense to skip that step and go directly to 4.0.13? Seems like I *might* miss some deprecation warnings if I do that, but if it saves major headaches the tradeoff might be worth it. Opinions?
Hassan Schroeder ------------------------ email@example.com
Consulting Availability : Silicon Valley or remote