For me, I’ll be waiting for at least a point release in Ubuntu before I ever consider migrating any machines. Then I’ll check against the forums and any security announcements.
Patch the test env first and test used functions and for known bugs.
What kind of systems are we talking about here? Mission critical client facing servers that if one goes down for 10 minutes you’re likely to get people canceling? Or just a home web server?
At home I virtualize everything. So I just make a snapshot, update, then if something goes wrong I can roll back. 30 minutes of downtime isn’t gonna kill me.
At work we have A/B systems. So we can update A, test it internally, if it’s good then swap to make them front facing. If nobody screams then we update B. If someone screams it’s a flick of a switch and maybe a minute of downtime.
I’m working my way towards maintaining more mission critical, so just want to do my best as I take my deployment more seriously. Test systems are working fine for me, but happy to get advice and suggestions from others with more experience.
i would create a duplicates of my machines and then test the updates on the duplicates first.
Makes sense. I’ve been doing this with a couple small boxes with same basic specs at home. Start with the least important, after making a snapshot, and go from there.