Hi, For what I could see in your explanation you are expecting the update task to teach people about the changes between some pre-releases. I don't think it is sustainable to do that. I'm all for improving the update task to give better feedback when do a minor version upgrade.
I believe we have almost all this information in the upgrading guide, so do you think that a link to the upgrade guiding after the command finish would be a good way to improve the process? On Mon, May 16, 2016 at 1:00 PM Hiren Mistry <[email protected]> wrote: > Hi, > > I would like to present a feature request to the `rails rails:update` > command. This feature request is about user experience and making > developers lives better. It goes alongs the same lines as your recent > migration from `rake` to `rails`, which has been an absolute joy to use, > much, much more than something that runs a fraction of second faster. > > I think it would be really nice if the `rails update` command provided > more user feedback for files that it does not update. Some examples: > > 1. if it printed out in STDOUT that I should change the > data-turbolinks-track from true to reload in my `application.html` > file because it wasn't able to find the `application.html.erb` file. (I > used HAML, SASS, and Rspec in my rails app.) > 2. code in `cable.coffee` has changed and needs to be replaced with > `cable.js`. > 3. mention there has been additions like > config/initializers/ssl_options.rb and > config/initializers/to_time_preserves_timezone.rb files, but it's not > needed for my application because... (post a link to refer to) and that's > why it did not create them. > > Basically with better feedback, we can save all the developers time and > anxiety when upgrading. With a little feedback like this, dev's know there > are additional changes that needs to be done that the script wasn't able > to, or new things/configuration changes with reference links to research so > they can determine what they wish to do about it. When upgrading becomes > easier and pleasant, then more dev's will be willing to upgrade quicker > which results in less support for older versions. > > Regards, > Hiren. > > PS - I got this insight from my recent experience updating rails (see issue > #24983 <https://github.com/rails/rails/issues/24983>). > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/rubyonrails-core. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
