
It is still possible to make something very much like Leap 15 from the ALP sources if there is enough community interest in helping to support packages. It in many cases may even be migratable from Leap 15, A couple of us worked on a proof of concept during SUSE's last hackweek look forward to a talk on it at this years conference.
-- Simon Lees (Simotek) http://simotek.net
@Dominique Thanks for the detailed response on the question. @Simon Thanks also for your response, it seems like the "something very much like Leap 15" is what a number of posters here, and myself, would be interested in . . . i.e, the logical extension of the current Leap concept/technology. I'm running both TW and Leap 15.5 . . . and somewhere "in between" would be the "sweet spot" for me, the end user on aging hardware. I also run Debian Bookworm and Sid . . . seems like of late Sid is "more stable" than TW, but let's say they are roughly "equivalent" . . . Debian has "unstable," "testing" and "stable" . . . "testing" is the famed "middle way" . . . having newer packages, but which have first have run through the crucible of "unstability" . . . . That's where the "gently rolling" concept of future iterations of Leap would come in, i.e., not a total rewrite of the system, for each new day (or whatever it is) vs . . . rolling in new packages to a generally "stable" base, that doesn't run into massive package upgrades every few months, etc. On the new idea of Leap 16 using "containers" . . . have yet to mess with that concept in linux. It sounds like what Apple did with the last of the OSX variations, where they went to apfs formating and it was possible to set up . . . ??? semi-fluid "containers" that were not "solid" like a "partition" . . . but would be similar, place to install a distro?? Apfs formatting seemed to just mess up the system . . . . So, the point of containers is that they are "easier" to make and/or erase?? Or, this is something to do with SSD technology, where "boundaries" like partitions have less meaning, and all of the data is actually "shared" by the entire disk, so containers just gently sketch in the general area where the data will be stored, but it isn't just there, it's everywhere??