3 ms·
> how many hours of work went into this upgrade process then? It's hard to say, but I generally agree with upgrading regularly instead of waiting until you're
by AlchemistCamp 7y ago
> how many hours of work went into this upgrade process then?
It's hard to say, but I generally agree with upgrading regularly instead of waiting until you're so far behind that it's an ordeal.
- atonse 7y agoAgreed. The problem happens with convincing your clients to pay you to do so. I have a client that I've been telling for 2+ years to upgrade from Rails 4.2.3 (and Ember 2.8), but they only now funded it. So I'm having to do 3+ years of upgrades and it's a huge headache. And at the end of it, if I've done my job correctly, the app will look identical.
- bdcravens 7y agoI would point clients to the Rails support policy, and have the same support policy. https://guides.rubyonrails.org/maintenance_policy.html https://guides.rubyonrails.org/maintenance_policy.html
- KurtMueller 7y agoRails at least has upgrade guides and a script that allows you to upgrade the app. It helps to go from one point relase to the next. I also find the Railsdiff web app helpful in comparing changes from one release to another. It's definitely not perfect or pain free though. I also hope you have a good test suite :). Good luck.
- ksec 7y agoI have been wondering, if it is possible to charge client on yearly upgrade. Or Maintenance fees on a Framework / Security bases. Try to sell it to them like iOS update, you get security update from each framework upgrade. And should this not be a easier sell?
- aflag 7y agoIt sounds nice to keep up. But I'm not sure if it's more efficient or not. Do you know about any study on this?