5 ms·

I tell you what, say what you will about having plenty of warning, but right now I'm big-bang-ishly updating an app to 5.2 and I'm mired in quicksand due to the

• jrochkind1 7y ago
  I agree that conflicts/integrations between dependencies tend to give more upgrade pain than conflicts with local code and a single dependency. I think probably exactly how often to upgrade all your dependencies on what schedule... depends on the particular product and organization and resource-richness. What Github's did, upgrading Rails _daily_ to the latest non-release master... sounds really attractive if you can do it, but I suspect most people can't. A step on the way would be just `bundle update`ing daily and making sure to keep up with always having that passing and deployed. (Although in Github's case I don't think the actually deployed with dependency on unrelased master). I don't actually really even do that, def haven't automated it (although it occurs to me it would be simple to automate on travis or probably equivalent).