i'm (re-, re-re-)reading up on these^ just-announced CloserTogether/NewLeap/Jump plans. given current plans, I'm trying to get a sense for whether we end up with more/less 'flexibility'. i know the question's been/being asked; i don't yet fully understand the answer. i realize the plans are in flux. here's my use-case. for opensuse-based production, none of the current releases -- out of the box -- meet my requirements. instead, currently, use a stable Leap core, with add'l repos -- devel or my own -- as needed. that approach is bumping into evermore significant limitations. particularly around 'base' tech'y. e.g., i use Kernel:Stable on Leap, with a rebuilt base:System Dracut, and the firmware upgrades that install along with it. i've switched to systemd-networkd rather than wicked for network mgmt. PRE-jump plans, Leap 15.2 remains stuck at Systemd v234 -- as that's the stable SLE-15* release. Afaict, it STAYS at that version for the entire 15x lifetime; unless/until there's a security-mandated update. with wireguard now native in-kernel, i'd like to use systemd-networkd's native WG support. but that's NOT available until systemd v>= 237; TW, of course, is at 244/245 already. does this CloserTogether "future" make it more, or less, likely that the 'Jump' release will have the flexibility to swap/enable version upgrades of key/core components -- in this case, systemd? or does Jump continue to stay stuck on old versions, leaving TW as the only choice of released version for newer base/core tech? yes, i can DIY my own opensuse systemd pkgs for Leap. working on it. going less well atm than hoped :-/ far simpler to use a distro that provides that flexibility (do that currently with Arch, and in-house LFS). prefer to have an option for a suse-based solution. is Jump it? -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org