Ruby on Rails Thursday, August 2, 2018

On Thu, Aug 2, 2018 at 10:39 AM, Joe Guerra <JGuerra@jginfosys.com> wrote:
> I justed jumped to using rails '5.2.0' in my app.
>
> Is that bad?

Depends on whether you think "can't even start" is a "bad" thing :-)

Jumping 3 versions like that is unlikely to ever work. The least
painful way to upgrade is to

1) move to the last available dot release of your current version
e.g. 4.2.8 -> 4.2.10

2) fix *all* the deprecation warnings

3) move up ONE major/minor version, e.g. latest 5.0 (5.0.7)

4) run your tests and fix anything that broke

5) run `bundle outdated` and see what gems are candidates for
being updated

&lather.rinse.repeat

--
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
twitter: @hassan
Consulting Availability : Silicon Valley or remote

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CACmC4yAzFLh5KUdsjMSy%3DmbERd7rjwapuStETnOUqv%3DB4JV6wQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment