Hello all, On 14/03/2026 16:59, Jeremy Bícha wrote:
On Sat, Mar 14, 2026 at 11:38 AM Steve McIntyre <[email protected]> wrote:The question is: will it be supported appropriately? We shouldn't be shipping things that we don't maintain and test.What about enabling Debian Live Lomiri for Testing and deferring the decision about publishing stable releases until later? I think that wouldn't burden those doing releases? I believe the Debian Lomiri team can commit for the lifetime of the forky development cycle to working on the Debian Lomiri experience. I think there is benefit in providing a way for people to try out current Lomiri without needing to install it first. No one else is providing that at this time. Maybe it is unnecessary to publish Debian Live releases for every desktop for every Debian Stable point release, but I think that should be a separate thread.
When I was talking to Mike in Brest DebConf25, I proposed to enable automated testing before publishing images and using the users as alpha/beta-testers. For me the ideal order would be: 1) The DE team states that the desktop is ready 2) Live images can be generated manually (in rebuild.sh) 3) The live images are reproducibly built (Jenkins helps here) 4) The live images have suitable tests in openQA (with images triggered by Jenkins) 5) Official live images are built by the debian-cd team (and then tested with openQA) first for testing/sid 6) Official live images are built by the debian-cd team for stable (when the DE migrates to stable) 7) Official live images are built by the debian-cd team for oldstable (when the DE migrates to oldstable) X) The DE is available in tasksel (X somewhere around 4 or 5) Currently 1), 2) and X) are fulfilled. I propose to wait with the step to publish a Lomiri live image in weekly builds (which have a few high visibility) until there is sufficient automated quality assurance. I can help with setting up 3) and 4) With kind regards, Roland Clobus
OpenPGP_signature.asc
Description: OpenPGP digital signature
