Since the early times of stable btrfs and after some major problems with ReiserFS 3 I have been doing manual transactional updates on my gentoo system using btrfs and I still do. I simply make a snapshot where the upgrade take part in a chrooted environment.
Nowadays I also have a laptop with OpenSuse Slowroll where I currently do transactional-updates to secure that I always have a working old present after the upgrade. I also disabled the automatic repo update on as I strive for consistency on the running root.
The main reason to go with TW/SL is that leap 16 is a year ahead and I really need up to date KDE 6 with proper wayland. Laptop 3K screens are just not fit for us over 50 and KDE 6 with Wayland has so much better support for scaling.
Now there are indications (in this forum thread and in this bug/feature request that this package is both unsupported for TW and SL (with writable root) and also part of the closed Kubic project thus potentially to be removed.
I still want to secure that I always can boot into a working system when upgrades goes wrong (and to be honest, OpenSuse TW, SL and Leap has failed to boot way more than expected).
In what way will I achieve my needs with btrfs snapper that is automatically installed and continues to be available?
Snapper appears to make a snapshot before and after any system changing activities so do I really need to also use the transactional-update?
As long as I can boot into an earlier known working configuration when the current configuration fail I will do just fine.