Re: Porter roll call for Debian Bookworm
Hi YunQiang Su On Sun, 26 Dec 2021 at 11:17, YunQiang Su wrote: > > For mipsel and mips64el, I > - test most packages on this architecture > - run a Debian testing or unstable system on port that I use regularly > - fix toolchain issues > - triage arch-specific bugs > - fix arch-related bugs > - triage d-i bugs > - test d-i regularly > - fix d-i bugs/issues > - maintain buildds > - maintain/provide hardware for (or assist with) automated tests on ci.d.n, > jenkins.d.n (etc.) > > I am a DD. Thanks for your response! In case #1000435 (matplotlib crashes on mips64el) is not already on your radar, would you please take a look? Regards Graham
Re: Porter roll call for Debian Bookworm
Hi A friendly reminder about the porter roll call for bookworm. On Sat, 2 Oct 2021 at 11:57, Graham Inggs wrote: > We are doing a roll call for porters of all prospective release > architectures. If you are an active porter behind one of these > architectures [1] and intend to continue for the development cycle of > Debian Bookworm (est. release mid-2023), please respond with a signed > email containing the following before Saturday, January 1, 2022: Please note we don't automatically assume that porters for previous releases will continue to do so. If you were a porter for a previous release, we'd like you to sign up again for bookworm. Please refer to the architecture requalification page [1] for the current status. Graham, on behalf of the release team [1] https://release.debian.org/bookworm/arch_qualify.html
Porter roll call for Debian Bookworm
Hi We are doing a roll call for porters of all prospective release architectures. If you are an active porter behind one of these architectures [1] and intend to continue for the development cycle of Debian Bookworm (est. release mid-2023), please respond with a signed email containing the following before Saturday, January 1, 2022: * Which architectures are you committing to be an active porter for? * Please describe recent relevant porter contributions. * Are you running/using Debian testing or sid on said port(s)? * Are you testing/patching d-i for the port(s)? Please note that no response is required for amd64 because our toolchain maintainers are happy to support amd64 as-is. Feel free to use the following template as your reply: """ Hi, I am an active porter for the following architectures and I intend to continue for the development cycle of Debian Bookworm (est. release mid-2023): For , I [delete/modify as appropriate] - test (most|all) packages on this architecture - run a Debian testing or unstable system on port that I use regularly - fix toolchain issues - triage arch-specific bugs - fix arch-related bugs - triage d-i bugs - test d-i regularly - fix d-i bugs/issues - maintain buildds - maintain/provide hardware for (or assist with) automated tests on ci.d.n, jenkins.d.n (etc.) - run other automated tests outside the Debian QA services (Please describe these) - ... """ Graham, on behalf of the release team [1] https://release.debian.org/bookworm/arch_qualify.html
Re: Porter roll call for Debian Bullseye
Hi A friendly reminder about the porter roll call for bullseye. On Mon, 2 Nov 2020 at 22:23, Graham Inggs wrote: > We are doing a roll call for porters of all release architectures. If > you are an active porter behind one of the release architectures [1] > for the entire lifetime of Debian Bullseye (est. end of 2024), please > respond with a signed email containing the following before Friday, > November 27: Please note we don't automatically assume that porters for previous releases will continue to do so. If you were a porter for a previous release, we'd like you to sign up again for bullseye. Please refer to the architecture requalification page [1] for the current status. Graham, on behalf of the release team [1] https://release.debian.org/bullseye/arch_qualify.html
Porter roll call for Debian Bullseye
Hi We are doing a roll call for porters of all release architectures. If you are an active porter behind one of the release architectures [1] for the entire lifetime of Debian Bullseye (est. end of 2024), please respond with a signed email containing the following before Friday, November 27: * Which architectures are you committing to be an active porter for? * Please describe recent relevant porter contributions. * Are you running/using Debian testing or sid on said port(s)? * Are you testing/patching d-i for the port(s)? Please note that no response is required for amd64 because our toolchain maintainers are happy to support amd64 as-is. Also note that this waiver no longer applies for i386, where it did in previous releases. Feel free to use the following template as your reply: """ Hi, I am an active porter for the following architectures and I intend to continue this for the lifetime of the Bullseye release (est. end of 2024): For , I - test (most|all) packages on this architecture - run a Debian testing or unstable system on port that I use regularly - fix toolchain issues - triage arch-specific bugs - fix arch-related bugs - triage d-i bugs - test d-i regularly - fix d-i bugs/issues - maintain buildds - maintain/provide hardware for (or assist with) automated tests on ci.d.n, jenkins.d.n (etc.) - run other automated tests outside the Debian QA services (Please describe these) - ... """ Graham, on behalf of the release team [1] https://release.debian.org/bullseye/arch_qualify.html
