Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130524
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Mime-Version: 1.0 (1.0)
Date: Tue, 31 Mar 2026 19:13:35 +0200
Subject: [PHP-DEV] Re: Release Managers for PHP 8.6
Message-ID: <E7DACA4A-8D0C-4ABE-A3AB-CBCA705BFF1F@gmail.com>
To: internals@lists.php.net
From: patrickmartin35@gmail.com (Patrick Martin)

Hi Volker,

I=E2=80=99d like to put myself forward as a candidate for the rookie Release=
 Manager position for the 8.6 release.

While I don=E2=80=99t yet have direct experience with php-src, I=E2=80=99ve b=
een working with PHP professionally for 9+ years and have a solid understand=
ing of the ecosystem.

I=E2=80=99m interested in getting more involved with php-src in the future a=
nd see this as a great opportunity to learn while contributing to the projec=
t.

Thanks for considering my application.

Patrick

On Tue, 03 Mar 2026 15:38:58 +0000, Volker Dusch 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
> [1].
>
> To perform the tasks outlined in [1], candidates should:
> - be confident contributing to and working with the PHP internals mailing l=
ist.
> - 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 candidate=
.
> An initial "TODO" page exists on the wiki and contains provisional
> dates for GA and pre-releases [2].
>
> You can apply until the 30th of March. Voting will start on the 31st of Ma=
rch.
>
>
> If you have any questions on the process, check out the post from my
> co-RM Daniel [3] that goes into more detail. Also, feel free to reach
> out to me, or Daniel, if you have further questions.
>
> [1] https://github.com/php/php-src/blob/master/docs/release-process.md
> [2] https://wiki.php.net/todo/php86
> [3] https://scherzer.dev/Blog/20260218-release-manager-notes
>
> PHP is a community-driven project, and your help would be greatly apprecia=
ted.
>
> Your 8.5 RMs,
> Volker, Daniel, and Pierrick