Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130525
Precedence: list
MIME-Version: 1.0
References: <CAMmyQQL2QGJ2PWUgwj8Ypd7Q_JNGEfTY76TXvg0Dzbea161w4w@mail.gmail.com>
In-Reply-To: <CAMmyQQL2QGJ2PWUgwj8Ypd7Q_JNGEfTY76TXvg0Dzbea161w4w@mail.gmail.com>
Date: Tue, 31 Mar 2026 19:25:26 +0200
Message-ID: <CAMmyQQL3Xd+OMBSetGfUHyWWBpTgs8eTtjVQeuJAY_6KqVbfWQ@mail.gmail.com>
Subject: [PHP-DEV] Re: Release Managers for PHP 8.6
To: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: edorian@php.net (Volker Dusch)

Hi everyone,

With Sara's mail and a last minute application from Patrick coming in,
I'm hereby closing the application period.

The voting thread will be started soon.

Thank you to everyone who applied!

Kind regards,
Volker

On Tue, Mar 3, 2026 at 4:38=E2=80=AFPM Volker Dusch <edorian@php.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
> [1].
>
> To perform the tasks outlined in [1], candidates should:
> - be confident contributing to and working with the PHP internals mailing=
 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 candidat=
e.
> 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 M=
arch.
>
>
> 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 appreci=
ated.
>
> Your 8.5 RMs,
> Volker, Daniel, and Pierrick