I would follow option 3 as well. There are too many new things between 3.2 and 5.2. You might try option 2 but 3 seems longer but safer. Don't forget to run the tests at each change :D
The Rails Upgrading Guides plus the release notes for each version in the Rails blog, possibly the changelogs in GitHub and the search engine will be your best friends :D
I had to upgrade from 4.1 to 5.2, it was not a major problem, I recommend you follow the official guide that @rhymes
mentioned, on the other hand, generate a new project in each version and compare only the base files, that will help a lot.
I would follow option 3 as well. There are too many new things between 3.2 and 5.2. You might try option 2 but 3 seems longer but safer. Don't forget to run the tests at each change :D
The Rails Upgrading Guides plus the release notes for each version in the Rails blog, possibly the changelogs in GitHub and the search engine will be your best friends :D
Good luck!
Thanks you @rhymes
☝️ THIS!
I had to upgrade from 4.1 to 5.2, it was not a major problem, I recommend you follow the official guide that @rhymes mentioned, on the other hand, generate a new project in each version and compare only the base files, that will help a lot.
One step at a time, good luck!
+1 on all this