Comment by phoronixrly

The point is that you don't have to: the unattended-upgrades part is separate from the major upgrades. You still get security updates for the previous stable release for a while after a new stable release, and the security updates can safely be installed the minute they're announced without bringing in unwanted features changes.

debian stable? Yes. Debian stable is tested to the point that it's fossilized. Besides, we're not even talking about a major version update. We're talking a minor one, and the last time I'd had a simple update break linux was when arch was shipping the master branch of grub. (The dev and I had words over this practice, which resulted in me going to another distro)

Since I switched to nixos some years ago, yes. My fear level dropped from 80% to 1%.

On my home server, sometimes I do take some snapshots and upgrade a few VMs and LXC containers.

Sometimes I even run testing because stable will be out shortly and I don't feel like upgrading.

It's a very different experience to the single Windows laptop in my house, where the latest stable is always subtly broken in ways I notice. Last week the top half of the taskbar disappeared for an evening, for example.

He did say Debian, being stable is the one thing it's good at.

I admin a bunch of Ubuntu servers and I tend to do a major version upgrade on my laptop and then some low priority machines to see if anything has changed. Typically, the only issues I've had is when there's dropped support for older SSH/SSL protocols which is easily fixed.

However, Windows Update isn't doing a major version upgrade as far as I know - it's the equivalent of doing a kernel upgrade in Linux. Also, the typical Linux upgrade command will also pull in updates/fixes for pretty much every bit of software in the system, whereas Windows Update will ignore user installed software as far as I know.

Once a new major version hits stable, it's been hammered on quite a bit. Debian has a reputation for being behind the curve, for this reason.