Hey, This follows on from the update back in Feburary [1].
1: https://lists.gnu.org/archive/html/guix-devel/2025-02/msg00539.html One big thing since then is that Git repositories and issue tracking has moved to Codeberg. This impacts QA since it's patch review and branch management is built around Debbugs/Mumi. Per GCD 002 [2], the guix-patches mailing list will continue to work until the end of this year, and my thinking is that QA will continue to support testing patches that are sent in while the mailing list remains operational. 2: https://codeberg.org/guix/guix-consensus-documents/src/branch/main/002-codeberg.md#issue-tracker-migration-path I've started trying to use Codeberg's issue and project tracking functionality for the qa-frontpage [3][4], and the related bordeaux build farm [5]. 3: https://codeberg.org/guix/qa-frontpage/projects/18699 4: https://codeberg.org/guix/qa-frontpage/issues 5: https://codeberg.org/guix/maintenance/projects/18702 This is very much an experiment, I'm still working out how these Forgejo features work and how to best make use of them. I'd encourage others to get involved, submit issues and comment on them. I presume there's permissions issues and I don't know how to address that, but if you aren't able to do something you'd like to do, let me know and I'll see if I can figure something out. I would like to see some setup for testing Pull Requests raised on Codeberg, although it's not clear to me how to approach this and I want to focus on finishing off the work on the existing setup [6]. Some work towards this has already happened [7], but I'm not aware this is up an running anywhere yet. 6: https://codeberg.org/guix/qa-frontpage/issues/3 7: https://codeberg.org/guix/data-service/pulls/2 Thanks, Chris
signature.asc
Description: PGP signature
