1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.BOOT

  • Re: Are follow-up steps for Lomiri/Phosh desktop required?

    From Cyril Brulebois@21:1/5 to All on Sun May 25 17:40:01 2025
    Hi,

    Roland Clobus <[email protected]> (2025-05-25):
    I also assumed that the MRs would have been on the radar of the
    relevant teams, but (given some discussion on debian-devel some time
    ago) every DD needs to explicitly enable notifications in Salsa, so
    that was apparently not the case.

    As far as I'm concerned, the primary point of contact in Debian is the
    BTS. Sure, MRs are nice to get reviews, to get some iterations done,
    etc., but I don't think it's reasonable to fire up MRs and hope they'll
    be picked up automatically. (This is orthogonal to whether we have
    enough workforce to wade through MRs and/or BTS entries.)

    I would feel most comfortable when the corresponding live images are
    being tested in openQA, but we have a chicken-egg issue here.

    See my lightning talk in Hamburg 17:38-18:52: https://meetings-archive.debian.net/pub/debian-meetings/2025/MiniDebConf-Hamburg/hamburg2025-32-lightning-talks.webm
    Let's have a release goal for forky to have desktop environments included/excluded based on tests in (at least) openQA (easy in-easy out)

    I can try to locally generate/mimic the updated task packages and
    build a live image from that (which I once did for the Lomiri
    desktop). I'll need a few day for that (since in IRL I'm also busy :-)

    Depending on your availability, what we could try is adding the two
    desktops, making that testable (if having them in sid is enough).

    I forgot to mention in my first reply: if the images team is worried
    about possible side effects that could result from adding choices (e.g. disturbances in the image build system — via debian-cd), that'd be
    another reason against including those tasks. I'm cc-ing debian-cd@ for
    input.

    (I don't want to speak for them, but I'd call that unlikely. My vague recollection was probably more about having to build images for each
    desktop environment, which we dropped a while back.)

    Looking at the timeline, would it be possible to add the two desktops
    in a point release of trixie and have this not delay the release of
    trixie?

    While I'm more than happy to consider backports during point releases,
    it would look very weird to me to have brand new desktops added there.


    Cheers,
    --
    Cyril Brulebois ([email protected]) <https://debamax.com/>
    D-I release manager -- Release team member -- Freelance Consultant

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmgzOAYACgkQ/5FK8MKz VSCqSRAAwdlW6nVEdpOC5i6F3X8TsyFNeYFobwjD7hn51tojGibRPTGhhqpbKMVn 7gxDjP2cnJ8LxyuKSt0ECizIe9r+etvvSVcFM0ZV2Nqknp997uPWO/HY/WTT41vK peY2NXCZ7yS0eGafSxmS1JWFjN03Cuiq1LMP+R6637donz88Lr9GXuOkYI6Yw7G9 MaE1ZZPm+j7S4mgsbfS7ANinbk8TQJWh9IBjCqoCLU8vNILLwM29UcArHX336wuW flmDG/LMarVjB3Nb2a746tHE2Z3IKr/FWvlLWEe9IBru6pnpsXzpIQvKUxQ6/mBP V5ol+bNX+OBaTYNV0e9qI4x+IBPETUW3WMP1SnTfAoVgvS9EKeawKlXzy39NZLee 0ROSLKzWZHCOG9sepK2clINJ4Al8qeATi8rcN8vDJ5ftOmuzPi9FtPBgpKBKAwup lDM3xXa9mGzAJHBG7GGb7WrW87AdINb/fQpdpaEptsqmgiqbF2JEPwOY0xrs1B8X 6HeFZT6cv3gFEOJmlecHbjwuEpQFYLKR4N24Z26f3QHomKjYKDsL283cA0eiq4w6 5vHxkv81tm+F90T2YRgVuxVBdcQjP9jCI1K3nqR37ndHRX8WYGfQUO6zfXqag9xU KiVnGhqOJWsdf5KbBfFxbbeR/fEUnM+omjx/URpASJ3ymw4gWVE=
    =eTKL
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    *
  • From Guido =?iso-8859-1?Q?G=FCnther?=@21:1/5 to Roland Clobus on Sun May 25 22:50:01 2025
    Hi,
    On Sun, May 25, 2025 at 11:59:39AM +0200, Roland Clobus wrote:
    Hello,

    On 25/05/2025 10:46, Guido G�nther wrote:
    On Sun, May 25, 2025 at 07:30:22AM +0000, Mike Gabriel wrote:
    [..snip..]
    Unless someone strongly feels differently, and convinces me to rethink this, I'll drop both entries from the wishlist for Trixie.

    I raise my hand here, because I strongly feel different regarding the Lomiri
    part of this mail. Thanks for sending this mail, so there still is some chance to turn the wheel (hopefully!).

    Same here. I understand that it's late in the cycle but then the recent feedback in the MR asking for addition to the Trixie TODO list made me believe there's nothing else to do for the moment.

    It was me who found the MRs, and proposed to add them to the wishlist (and then started this confusion).

    I also assumed that the MRs would have been on the radar of the relevant teams, but (given some discussion on debian-devel some time ago) every DD needs to explicitly enable notifications in Salsa, so that was apparently
    not the case.

    I would feel most comfortable when the corresponding live images are being tested in openQA, but we have a chicken-egg issue here.

    See my lightning talk in Hamburg 17:38-18:52: https://meetings-archive.debian.net/pub/debian-meetings/2025/MiniDebConf-Hamburg/hamburg2025-32-lightning-talks.webm
    Let's have a release goal for forky to have desktop environments included/excluded based on tests in (at least) openQA (easy in-easy
    out)

    OpenQA tests would be great. Let me know if I can help with anything.

    Cheers,
    -- Guido


    I can try to locally generate/mimic the updated task packages and build a live image from that (which I once did for the Lomiri desktop). I'll need a few day for that (since in IRL I'm also busy :-)

    Looking at the timeline, would it be possible to add the two desktops in a point release of trixie and have this not delay the release of trixie?

    With kind regards,
    Roland Clobus

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)