Packages where stable to stable+1 is a bigger-than-supported upgrade Re: Unsing stable-backports as an ugprade path to stable+1

["Rebecca N. Palmer" <rebecca_palmer@zoho.com>]

Another option might be to have a ceph18 that exists solely to allow the 
upgrade script to do whatever data/config conversion needs to be done in 
2 steps, i.e. ceph 16.x -> ceph18 -> ceph 19.x.  (Possibly have ceph18 
have a nonstandard name/path, both to avoid file conflicts and so it 
doesn't accidentally get run by actual users, and consider disabling the 
service during the upgrade to minimize the impact of any security flaws 
in ceph18.)

(For ceph in particular the risk of "getting it wrong = data 
loss/corruption" might be high enough that it's better to not ship ceph 
in stable, but it might not be the only package where upgrades skipping 
2-3 years of releases are unsupported.)