Re: Porter roll call for Debian Bullseye

2020-12-12 Thread Frédéric Bonnard
Hi,
sorry for the late reply and thanks a lot Graham for pinging me
directly. I didn't monitor -devel closely lately, but

I am an active porter for the following architecture and I intend
to continue this for the lifetime of the Bullseye release (est. end
of 2024):

For ppc64el, I
- test most packages on this architecture
- run a Debian testing or unstable system that I use regularly
- fix ppc64el-related bugs, especially by following 
https://udd.debian.org/cgi-bin/ftbfs.cgi
- test d-i on a daily basis with an homegrown automated iso
  (sid netboot/testing netinst/bullseye alphas) installer
  (vm and PowerVM) and moving to OpenQA now.
- fix d-i bugs/issues

I am a DD,

Frédéric Bonnard


signature.asc
Description: PGP signature


Re: Porter roll call for Debian Bookworm

2021-10-14 Thread Frédéric Bonnard
Hi,

I am an active porter for the following architecture and I intend to
continue for the development cycle of Debian Bookworm
(est. release mid-2023):

For ppc64el, I
- test most packages on this architecture
- run a Debian testing or unstable system that I use regularly
- fix ppc64el-related bugs, especially by following 
https://udd.debian.org/cgi-bin/ftbfs.cgi
- test d-i on a daily basis with OpenQA
  (sid netboot/testing netinst/bookworm alphas) installer
  (vm and PowerVM on P8, P9, P10)
- fix d-i bugs/issues

I am a DD

Frédéric Bonnard

On Sat, 02 Oct 2021 11:57:07 +0200 Graham Inggs  wrote:
> 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
> 


signature.asc
Description: PGP signature