• Handling GNOME uploads during Hard Freeze

    From =?UTF-8?Q?Jeremy_B=C3=ADcha?=@21:1/5 to All on Tue May 20 23:10:01 2025
    I think we need to set guidelines for how we want to handle Debian
    GNOME uploads now that we entered Hard Freeze.

    Sometimes it is useful to upload packages to experimental that are
    intended for upload to unstable soon. For instance: gtk4. By uploading
    to experimental first, we can verify that the package builds on all
    release architectures and that triggered autopkgtests are passing on
    amd64 & arm64.

    Most of our packages are either key packages or do not have
    non-trivial autopkgtest so they would need someone to file an unblock
    request and the Release Team approve it in order for any uploads from
    now on to be eligible for migration to Testing.

    I suggest that we don't do any uploads for the GNOME team packages to
    Unstable **or** Experimental unless we intend to file an unblock
    request for them. Ubuntu uploads can be made directly to an
    ubuntu/questing branch (this is my suggestion for packages that are
    already in sync since Trixie should be released before the Ubuntu
    26.04 development cycle gets very far) or an ubuntu/latest branch and
    then we can easily upload to Debian directly once Trixie is released.

    What do the rest of you think? Is it too conservative to avoid
    experimental for all packages? Or is it nicer to have a simpler
    guideline?

    References
    -----
    - https://release.debian.org/testing/freeze_policy.html#hard
    - https://release.debian.org/britney/pseudo-excuses-experimental.html

    Thank you,
    Jeremy BĂ­cha

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