Release Managers for PHP 8.3

I had volunteered in a previous cycle but, sadly, lost in the voting
round. That said, I'm still eager to be more heavily involved and up for
the challenge (both for the immediate process and for any long-term
support beyond the dates listed in the existing todo.

I've been working with PHP in userland since 2005 and dabbling in
internals (mostly to understand FFI and interoperability) since 2016.
I'm not a C guru as in I can't reliably write greenfield C code. But I
have worked with and on C/C++ teams and am well adept at groking
existing code, hunting for bugs, and ensuring that submitted code does
what it claims to do.

It would be an honor to even be considered for this role and I'd love to
earn your support!

~Eric Mann

Hi all,

It's time to start the process of finding and electing RMs for the next minor PHP release.

We are looking for three souls to take on this role. Whomsoever is elected will be guided and helped by the current, as well as previous RMs and the excellent documentation in release-process.md [1].

Candidates should have a reasonable knowledge of internals (without necessarily being a C guru), be confident about merging pull requests without breaking backward compatibility, doing triage for bugs, liaising with previous release managers, and generally getting the branch in good shape, as these are among the activities you will be undertaking as release manager.

Notably, at least one of the volunteers must be a "veteran" release manager, meaning they have participated in at least one release of PHP in the past. The other may be an additional veteran, or more ideally, someone new to the RM role (in order to increase our supply of veteran RMs).

Please put your name forward here if you wish to be considered a candidate. An initial TODO page has been added to the wiki and contains provisional dates for GA and pre-releases [2].

[1]https://github.com/php/php-src/blob/master/docs/release-process.md
[2]https://wiki.php.net/todo/php83

Let's all make PHP awesome!
Pierrick Charron, Sergey Panteleev & Ben Ramsey

--
Security Principles for PHP Applications
https://www.phparch.com/books/security-principles-for-php-applications/
*Eric Mann

• Tekton
  *PGP:*0x63F15A9B715376CA https://keybase.io/eamann
  *P:*503.925.6266
  *E:*eric@eamann.com
  eamann.com https://eamann.com
  ttmm.io https://ttmm.io
  Twitter icon https://twitter.com/ericmann LinkedIn icon
  <https://www.linkedin.com/in/ericallenmann/

Please put your name forward here if you wish to be considered a
candidate. An initial TODO page has been added to the wiki and
contains provisional dates for GA and pre-releases [2].

I'll throw my hat into the ring, since I had previously applied for the
PHP 8.2 release manager position.

I have familiarity with internals and a bit of the release process due
to packaging PHP as a downstream (supporting the IBM i platform) and
maintaining PECL extensions (ibm_db2/PDO_IBM). There's a lot of triage
of user issues (understanding them, providing solutions/patches, etc.),
so I feel I could assess PRs on the other side of review. I've also
thrown a lot of fixes back upstream, in particular with the ODBC
extensions. Currently I just worked on some patches to improve error
reporting with sessions/HTTP responses.

As such, I think my background would make me a good candidate.

~cb

Hi all,

I'd like to clarify the deadline for the volunteer search and the voting phase:

Applications will be accepted until 31 March 12:00:00 UTC

Elections (if needed) will start on 1 April and run until 16 April 12:00:00 UTC

Pierrick Charron, Sergey Panteleev & Ben Ramsey

Hi everyone,

I want to let you know that I'm interested in volunteering as the veteran
release manager for PHP 8.3. I would be honored to help the two new release
managers who will be joining the team, and strive to provide the same level
of support that Ben did for Sergey and me.

Cheers,
Pierrick

Le mer. 1 mars 2023, à 15 h 21, Sergey Panteleev sergey@php.net a écrit :

Hi all,

It's time to start the process of finding and electing RMs for the next
minor PHP release.

We are looking for three souls to take on this role. Whomsoever is elected
will be guided and helped by the current, as well as previous RMs and the
excellent documentation in release-process.md [1].

Candidates should have a reasonable knowledge of internals (without
necessarily being a C guru), be confident about merging pull requests
without breaking backward compatibility, doing triage for bugs, liaising
with previous release managers, and generally getting the branch in good
shape, as these are among the activities you will be undertaking as release
manager.

Notably, at least one of the volunteers must be a "veteran" release
manager, meaning they have participated in at least one release of PHP in
the past. The other may be an additional veteran, or more ideally, someone
new to the RM role (in order to increase our supply of veteran RMs).

Please put your name forward here if you wish to be considered a
candidate. An initial TODO page has been added to the wiki and contains
provisional dates for GA and pre-releases [2].

[1] https://github.com/php/php-src/blob/master/docs/release-process.md
[2] https://wiki.php.net/todo/php83

Let's all make PHP awesome!
Pierrick Charron, Sergey Panteleev & Ben Ramsey

Hello,

I would like to announce that I want to candidate to become a PHP 8.3
Release Manager. I have been contributing to PHP core for almost 10 years
and maintain some parts of PHP. Specifically FPM, JSON, OpenSSL ext and
some other bits. I'm part time funded by PHP Foundation and as part of that
I'm looking to document and improve the internal processes (some of them
will be soon proposed) which will also cover RM functioning and possibly
improving the release flow as well. That would be much better done from the
RM position and that's one of the main reasons why I candidate.

Regards

Jakub

Hi all,

It's time to start the process of finding and electing RMs for the next
minor PHP release.

We are looking for three souls to take on this role. Whomsoever is elected
will be guided and helped by the current, as well as previous RMs and the
excellent documentation in release-process.md [1].

Candidates should have a reasonable knowledge of internals (without
necessarily being a C guru), be confident about merging pull requests
without breaking backward compatibility, doing triage for bugs, liaising
with previous release managers, and generally getting the branch in good
shape, as these are among the activities you will be undertaking as release
manager.

Notably, at least one of the volunteers must be a "veteran" release
manager, meaning they have participated in at least one release of PHP in
the past. The other may be an additional veteran, or more ideally, someone
new to the RM role (in order to increase our supply of veteran RMs).

Please put your name forward here if you wish to be considered a
candidate. An initial TODO page has been added to the wiki and contains
provisional dates for GA and pre-releases [2].

[1] https://github.com/php/php-src/blob/master/docs/release-process.md
[2] https://wiki.php.net/todo/php83

Let's all make PHP awesome!
Pierrick Charron, Sergey Panteleev & Ben Ramsey