Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130242
Date: Tue, 3 Mar 2026 17:38:33 +0100
To: php internals <internals@lists.php.net>, Volker Dusch
 <edorian@php.net>
Message-ID: <6122d648-bb48-41f8-a80d-889531de3c65@Spark>
In-Reply-To: <CAMmyQQL2QGJ2PWUgwj8Ypd7Q_JNGEfTY76TXvg0Dzbea161w4w@mail.gmail.com>
References: <CAMmyQQL2QGJ2PWUgwj8Ypd7Q_JNGEfTY76TXvg0Dzbea161w4w@mail.gmail.com>
Subject: Re: [PHP-DEV] Release Managers for PHP 8.6
Precedence: list
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="69a70e8f_58a5e673_4e0"
From: jordikroon@me.com (Jordi Kroon)

--69a70e8f_58a5e673_4e0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi Internals,

I would like to be a candidate for the rookie 8.6 Release Manager positio=
n.

I have been following the php repositories (docs, src) for a while now an=
d have done a few contributions both on the repo as well as on the mailin=
g list.

I have experience with git and managing projects but I also have a lot to=
 learn. This position will help me get better in these skills with guidan=
ce of the veteran Release Managers.

=46eel free to ask me any questions.

Kind regards,
Jordi Kroon
On 3 Mar 2026 at 4:40=E2=80=AFPM +0100, Volker Dusch <edorian=40php.net>,=
 wrote:
> Hey folks,
>
> Every year in March we start the process of finding candidates who
> want to volunteer as Release Managers (RMs) for the next PHP release.
>
> We are looking for two new (rookie) RMs and one veteran RM.
>
> Should you be elected, you will be guided and helped by the current,
> as well as previous RMs and the documentation in release-process.md
> =5B1=5D.
>
> To perform the tasks outlined in =5B1=5D, candidates should:
> - be confident contributing to and working with the PHP internals maili=
ng list.
> - understand PHP's backward compatibility guarantees - including where
> they do not apply.
> - be able to triage bugs, in collaboration with core developers.
> - liaise effectively with previous release managers.
> - have a working knowledge of Git, including branching and merging.
>
> ... as these skills reflect the key responsibilities you will take on
> as a release manager.
>
> Ideally, at least one of the candidates for the rookie RM role should
> have some experience with php-src as the ability to assess more
> technical PR's will come in handy. Other candidates do not necessarily
> need to have deep knowledge of internals but should understand the
> above-mentioned points.
>
> You should be confident that you can volunteer a couple of hours on
> one Tuesday and Thursday every other month over the coming years.
> Additionally, extra time will be required in the month leading up to
> the .0 release as the alpha/beta/RC phases are more frequent and more
> decisions have to be made there.
>
>
> Please put your name forward here if you wish to be considered a candid=
ate.
> An initial =22TODO=22 page exists on the wiki and contains provisional
> dates for GA and pre-releases =5B2=5D.
>
> You can apply until the 30th of March. Voting will start on the 31st of=
 March.
>
>
> If you have any questions on the process, check out the post from my
> co-RM Daniel =5B3=5D that goes into more detail. Also, feel free to rea=
ch
> out to me, or Daniel, if you have further questions.
>
> =5B1=5D https://github.com/php/php-src/blob/master/docs/release-process=
.md
> =5B2=5D https://wiki.php.net/todo/php86
> =5B3=5D https://scherzer.dev/Blog/20260218-release-manager-notes
>
> PHP is a community-driven project, and your help would be greatly appre=
ciated.
>
> Your 8.5 RMs,
> Volker, Daniel, and Pierrick

--69a70e8f_58a5e673_4e0
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html xmlns=3D=22http://www.w3.org/1999/xhtml=22>
<head>
<title></title>
</head>
<body>
<div name=3D=22messageBodySection=22>
<div dir=3D=22auto=22>Hi Internals,<br />
<br />
I would like to be a candidate for the rookie 8.6 Release Manager positio=
n.<br />
<br />
I have been following the php repositories (docs, src) for a while now an=
d have done a few contributions both on the repo as well as on the mailin=
g list.<br />
<br />
I have experience with git and managing projects but I also have a lot to=
 learn. This position will help me get better in these skills with guidan=
ce of the veteran Release Managers.<br />
<br />
=46eel free to ask me any questions.<br /></div>
</div>
<div name=3D=22messageSignatureSection=22><br />
Kind regards,
<div dir=3D=22auto=22>Jordi Kroon</div>
</div>
<div name=3D=22messageReplySection=22>On 3 Mar 2026 at 4:40=E2=80=AFPM +0=
100, Volker Dusch &lt;edorian=40php.net&gt;, wrote:<br />
<blockquote type=3D=22cite=22 style=3D=22border-left-color: grey; border-=
left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left:=
 10px;=22>Hey folks,<br />
<br />
Every year in March we start the process of finding candidates who<br />
want to volunteer as Release Managers (RMs) for the next PHP release.<br =
/>
<br />
We are looking for two new (rookie) RMs and one veteran RM.<br />
<br />
Should you be elected, you will be guided and helped by the current,<br /=
>
as well as previous RMs and the documentation in release-process.md<br />=

=5B1=5D.<br />
<br />
To perform the tasks outlined in =5B1=5D, candidates should:<br />
- be confident contributing to and working with the PHP internals mailing=
 list.<br />
- understand PHP's backward compatibility guarantees - including where<br=
 />
they do not apply.<br />
- be able to triage bugs, in collaboration with core developers.<br />
- liaise effectively with previous release managers.<br />
- have a working knowledge of Git, including branching and merging.<br />=

<br />
... as these skills reflect the key responsibilities you will take on<br =
/>
as a release manager.<br />
<br />
Ideally, at least one of the candidates for the rookie RM role should<br =
/>
have some experience with php-src as the ability to assess more<br />
technical PR's will come in handy. Other candidates do not necessarily<br=
 />
need to have deep knowledge of internals but should understand the<br />
above-mentioned points.<br />
<br />
You should be confident that you can volunteer a couple of hours on<br />=

one Tuesday and Thursday every other month over the coming years.<br />
Additionally, extra time will be required in the month leading up to<br /=
>
the .0 release as the alpha/beta/RC phases are more frequent and more<br =
/>
decisions have to be made there.<br />
<br />
<br />
Please put your name forward here if you wish to be considered a candidat=
e.<br />
An initial =22TODO=22 page exists on the wiki and contains provisional<br=
 />
dates for GA and pre-releases =5B2=5D.<br />
<br />
You can apply until the 30th of March. Voting will start on the 31st of M=
arch.<br />
<br />
<br />
If you have any questions on the process, check out the post from my<br /=
>
co-RM Daniel =5B3=5D that goes into more detail. Also, feel free to reach=
<br />
out to me, or Daniel, if you have further questions.<br />
<br />
=5B1=5D https://github.com/php/php-src/blob/master/docs/release-process.m=
d<br />
=5B2=5D https://wiki.php.net/todo/php86<br />
=5B3=5D https://scherzer.dev/Blog/20260218-release-manager-notes<br />
<br />
PHP is a community-driven project, and your help would be greatly appreci=
ated.<br />
<br />
Your 8.5 RMs,<br />
Volker, Daniel, and Pierrick<br /></blockquote>
</div>
</body>
</html>

--69a70e8f_58a5e673_4e0--