Context is everything... On a disposable test system, its an update free for all. On a personal use daily driver, regularly, with some testing and daily backups available. On a business computer, only tested updates. On a production server, after full testing, updates are included in canned images. Security patches have a separate update stream. On production equipment embedded control systems, hell no unless the update includes needed functionality.As you can probably guess, my view is that "updates" (and whole new "major releases") are generally bad and to be avoided - unless you really need it (them).
Now, there are exceptions. In particular, there is one particular piece of software (which I won't mention by name, but it will be clear to at least some readers what it is) that I use on all my Pis and where you absolutely, positively, always have to be running the latest and greatest version. So, for that, I have a daily process that checks the site and updates if needed.
But other than that, no. I follow the "If it ain't broke..." theory religiously.
I am totally aligned with the "you don't want to be the first one" when it comes to updates, unless the vendor is building the patch specifically for you.
Statistics: Posted by bjtheone — Mon Jun 17, 2024 6:29 pm