The insidious urge to fix what ain't broke has arisen. I'll probably follow the official documentation, unless someone has a better suggestion.
I'm not running anything unusual and I haven't done much, if any, "customization". I update packages maybe a couple of times a week, so they're current.
Should I go ahead and put myself through this now, or wait until support is dropped and I'm forced?

you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 17 hours ago

The fewer packages you have installed, the easier it is to upgrade. So if your stuff is containerized, upgrade should be mostly painless.

In my history at least, dist-upgrades have never themselves been a problem, not even when doing such things as a x86-to-x64 crossgrade upgrade (from Stretch to Buster, back in the time). The problem usually comes right after, with the first reboot, when something does not generate correctly in Grub or the new kernel's initramfs is lacking a specific module, or a given mariadb flag you were counting on is no longer added by default, or somesuch. So always have a rescue boot ready.

  • source