Hi Rafael,
I'm not expecting much for pre-releases as they are a work in progress. My feedback is for checking these cases before final release (time/priority/resource permitting). I agree the ideal solution presented above is not sustainable for an open source project, but I wanted to put the idea out incase there are some easy wins.
To your suggestion of adding the link to the upgrading guide in the console output, absolutely do it - I think that's a super, super easy way of informing people. I can help with adding that in if you can point me to the file and area.
The next level would be to inform the user of which files did not get changed or were partially changed. It doesn't need to be complex, I'm thinking the script knows if a file was changed or not, so if we can capture the unchanged files and list them that's a start. Then printing something like this for my scenario:
The following files were not updated, please refer to the upgrade guide for changes and if it's applicable to you:
- application.html.erb
- cable.js
- ssl_options.rb
- to_time_preserves_timezone.rb
There may be other more simpler solutions of basically informing the user that `rails update` took care of these changes but these other ones were left out and you need to look into it. It greatly lowers the barrier to checking the upgrade guide by giving the user very tangible things to focus on.
I appreciate you listening to my idea and I do understand the situation from your side in adding features. Let me know if you need me to help with adding the link for now.
Regards,
Hiren