PHP 8.2 Release Manager Selection

2 years ago by Christoph M. Becker — view source

unread

Hi all,

with the first alpha of PHP 8.2 due in 6 weeks (unless we are going to
change our usual schedule), I think it's time to start the process of
finding and electing release managers for the next minor release of PHP.

We are looking for two 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/php82

--
Christoph M. Becker

2 years ago by Sergey Panteleev — view source

unread

Hi all,

Lately I've been doing documentation for PHP, keeping the Russian version up to date, and helping a little with the English, German and French versions.

I would also like to contribute and help in other areas, such as newbie RM.

If possible, my hat is in the ring.

—
wbr,
Sergey Panteleev

2 years ago by Mark Randall — view source

unread

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 could potentially be interested in helping out with this, but I do
have a question about it, mainly, why hasn't most of this been automated
at this point?

I was reading through the release process notes and am not seeing any
obvious blocks on most of it that could not be accomplished via a
suitable CI/CD pipeline.

Is it just a matter of someone having time available to do it?

The one thing which does make me ponder is would we need to assign a GPG
key to the build process?

I'd be happy to give some of my time later this year to further
investigate this.

2 years ago by Christoph M. Becker — view source

unread

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 could potentially be interested in helping out with this, but I do
have a question about it, mainly, why hasn't most of this been automated
at this point?

I was reading through the release process notes and am not seeing any
obvious blocks on most of it that could not be accomplished via a
suitable CI/CD pipeline.

Is it just a matter of someone having time available to do it?

The one thing which does make me ponder is would we need to assign a GPG
key to the build process?

I'd be happy to give some of my time later this year to further
investigate this.

There are docker images available[1] which automate parts of the build
process. However, doing the builds is only a rather small part of the
obligations of a release manager, and the other tasks (such as deciding
whether to merge a pull request, doing bug triage, and deciding on the
actual release schedule) cannot be automated.

[1] https://github.com/sgolemon/php-release

--
Christoph M. Becker

2 years ago by Aaron Junker — view source

unread

Hi Internals

I have some interest in doing this. I think I know PHP and git very well and I also know more or less how the PHP internal processes work. However I have two doubts/questions:

How much time do I need for this task? I can't really estimate this. I sure have would have some time to spare, but definitely not too much.
I don't really know C. The mail says you don't necessarily have to. I could learn it if necessary though. So how bad would it be if I couldn't program in or understand C?

It would be nice if someone could answer them. Thanks!

Best regards
Aaron Junker

2 years ago by Christoph M. Becker — view source

unread

I have some interest in doing this. I think I know PHP and git very well and I also know more or less how the PHP internal processes work. However I have two doubts/questions:

How much time do I need for this task? I can't really estimate this. I sure have would have some time to spare, but definitely not too much.

That very much depends. Doing the releases (every 2 weeks) may take an
hour or so (or much less if you're using some automation). The other
tasks may easily take more time, especially until the first GA release.
Note, though, that there is a second RM, so the work can be distributed.

I don't really know C. The mail says you don't necessarily have to. I could learn it if necessary though. So how bad would it be if I couldn't program in or understand C?

As release manager, there is no need to program in C, but you should
have at least a working understanding of C to be able to roughly assess
PRs and commits, and to be able to resolve merge conflicts, if these occur.

--
Christoph M. Becker

2 years ago by Aaron Junker — view source

unread

Hi internals

After answering my questions (Thanks Christoph) I would like to pose my application as release manager.

I'm a 17 year old college student from Switzerland.

I've experience in triaging issues and GitHub from triaging the Microsoft PowerToys repository [1][2] and the opensource.microsoft.com repository [3][4]. My GitHub handle is aaron-junker [5].

I'm very passionate about PHP and I love programming in PHP. That's why I would feel very honored to be a release manager for PHP 8.2.

I will soon start to learn the basics of C. That's something I wanted to learn anyway.

I would love to get taken in cosideration for this role.

Best regards

Aaron Junker

[1] https://github.com/microsoft/PowerToys
[2] https://github.com/microsoft/PowerToys/blob/main/COMMUNITY.md#aaron-junker---aaron-junker
[3] https://github.com/microsoft/opensource.microsoft.com
[4] https://github.com/microsoft/opensource.microsoft.com/blob/main/CONTRIBUTING.md?plain=1#L32
[5] https://github.com/Aaron-Junker

2 years ago by Evan Sims via internals — view source

unread

Hello! I'd be eager for the opportunity to be involved as a release
manager, and contributing to the PHP community I've made built my career
around.

I've been a PHP developer since 2000 (with the release of PHP4), and
although I do not work in C in my day to day anymore, I cut my
programmer teeth on the language and worked with it quite extensively
previously. Today I'm the lead PHP engineer for Auth0 (now an Okta
product group) in charge of our PHP SDKs. I previously worked for the
non-profit Ushahidi has a Senior Engineer on their PHP-based platforms.
Beyond this, and aside from my time as a technical video gamer designer,
most of my freelance professional career has been around building PHP-
based apps.

Naturally, I live in Git these days with my work, triaging bugs. I'm a
strong communicator and enjoy collaborating and engaging with the open-
source community.

Cheers,
Evan Sims

Hi all,

with the first alpha of PHP 8.2 due in 6 weeks (unless we are going to
change our usual schedule), I think it's time to start the process of
finding and electing release managers for the next minor release of
PHP.

We are looking for two 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/php82

--
Christoph M. Becker

--

To unsubscribe, visit: https://www.php.net/unsub.php

2 years ago by Calvin Buckley — view source

unread

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 put my name in the hat for applying to be an RM. I actually
package PHP as a downstream (for IBM i users), have tried to do what I
can for triaging issues (usually on behalf of my clients), and have
written some PRs for upstream. The skills there should be able to
inform the process as an RM, if I become one. I see some other good
candidates though, so I think 8.2 will be in good hands regardless.

2 years ago by Sergey Panteleev — view source

unread

Hey Christoph,

Do we choose one rookie for this release or two (as for 8.1)?

Also, maybe define some kind of deadline for submitting applications and the voting phase, thoughts?

—
wbr,
Sergey Panteleev

1 year ago by Saif Eddin Gmati — view source

unread

------- Original Message -------

Hi all,

with the first alpha of PHP 8.2 due in 6 weeks (unless we are going to
change our usual schedule), I think it's time to start the process of
finding and electing release managers for the next minor release of PHP.

We are looking for two 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/php82

--
Christoph M. Becker

--

To unsubscribe, visit: https://www.php.net/unsub.php

Hello,

I would like to introduce myself to those of you who might not know me, my name is Saif Eddin Gmati ( also known as "azjezz" ), i have been working with PHP for approximately 9 years.

I'm currently employed as a senior developer at Les Tilleuls, before that i worked at Symfony SAS, in total, i have over 3 years of professional experience.

I maintain some open source projects on my free time ( e.g: PSL ), and help contribute to some other on my free time ( e.g: Symfony, Psalm ).

I have been subscribed to the internals mailing list for few years now, and i think i can take on this role with the help of the veteran RM.

Note: our company ( https://les-tilleuls.coop ) has agreed to sponsor my role as RM if selected, which would make this much easier for me.

regards.

2 years ago by Eric Mann via internals — view source

unread

I'm new to this mailing list as I'd previously (and very mistakenly)
assumed it was meant for existing contributors. So I've always consumed
conversations via web-based aggregators rather than directly.

My mistake.

That being said, I am very interested in being a part of this release.
I've been using PHP since ~2005 and cut my teeth on PHP4. Since then,
I've covered everything from Fortran to VB.net and C# to Ruby to Python
to Golang. Today I write a mix of Python and PHP primarily (with a
smattering of Go and a curiosity about Rust). I'm not a C guru, but in
previous roles worked with several of them and can follow my way around
a C codebase. I've frequently gone spelunking through PHP's system to
help document various methods or interfaces exposed by the standard
library as well.

I am in no way a veteran PHP RM, but I am a fairly experienced RM with
private codebases. I live and breathe in Git, love automation, and have
been accused of more than a passing fancy in security as well. Somewhere
along the line I managed to coax php[architect] into publishing my book
on the OWASP Top Ten, and they still put up with my monthly security
column as well.

In other words, I'd love to be a part of this and am more than happy to
answer any and all questions y'all want to throw my way.

~Eric Mann

From: Sergey Panteleev sergey@sergeypanteleev.com
Date: Tue, Apr 26, 2022 at 11:27 AM
Subject: [PHP-DEV] PHP 8.2 Release Manager Selection
To: Christoph M. Becker cmbecker69@gmx.de, PHP internals
internals@lists.php.net

Hey Christoph,

Do we choose one rookie for this release or two (as for 8.1)?

Also, maybe define some kind of deadline for submitting applications
and the voting phase, thoughts?

—
wbr,
Sergey Panteleev

--
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/

2 years ago by Joe Watkins — view source

unread

Hi all,

Applications are open for a week.

Two people will be chosen by election and a veteran will help them.

If no other veteran comes forward I will continue in that role for 8.2.

Cheers
Joe

On Tue, 26 Apr 2022, 21:21 Eric Mann via internals, internals@lists.php.net
wrote:

I'm new to this mailing list as I'd previously (and very mistakenly)
assumed it was meant for existing contributors. So I've always consumed
conversations via web-based aggregators rather than directly.

My mistake.

That being said, I am very interested in being a part of this release.
I've been using PHP since ~2005 and cut my teeth on PHP4. Since then,
I've covered everything from Fortran to VB.net and C# to Ruby to Python
to Golang. Today I write a mix of Python and PHP primarily (with a
smattering of Go and a curiosity about Rust). I'm not a C guru, but in
previous roles worked with several of them and can follow my way around
a C codebase. I've frequently gone spelunking through PHP's system to
help document various methods or interfaces exposed by the standard
library as well.

I am in no way a veteran PHP RM, but I am a fairly experienced RM with
private codebases. I live and breathe in Git, love automation, and have
been accused of more than a passing fancy in security as well. Somewhere
along the line I managed to coax php[architect] into publishing my book
on the OWASP Top Ten, and they still put up with my monthly security
column as well.

In other words, I'd love to be a part of this and am more than happy to
answer any and all questions y'all want to throw my way.

~Eric Mann

From: Sergey Panteleev sergey@sergeypanteleev.com
Date: Tue, Apr 26, 2022 at 11:27 AM
Subject: [PHP-DEV] PHP 8.2 Release Manager Selection
To: Christoph M. Becker cmbecker69@gmx.de, PHP internals
internals@lists.php.net

Hey Christoph,

Do we choose one rookie for this release or two (as for 8.1)?

Also, maybe define some kind of deadline for submitting applications
and the voting phase, thoughts?

—
wbr,
Sergey Panteleev

--
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/

2 years ago by Pierrick Charron — view source

unread

Hi,

I would also like to present myself as a Rookie RM for PHP8.2

For those of you who don't know me, my name is Pierrick. I am French (that
explains my grammar mistakes) and have been living in Montreal, Canada for
15 years now and have been working with PHP since then.
I made my first contribution to the PHP Project in 2009 by submitting a
small patch. Since then I have touched multiple parts of the PHP project. I
patched a few bugs, contributed to the french documentation translation,
wrote/maintained some pecl extensions, maintained ext/curl from 2010 to
2016. I also submitted fews RFCs with their patches, some were approved and
others rejected. I'm not a C guru but have basic knowledge of it (I never
worked professionally with it). I also have some knowledge of PHP
internals, but I did not touch the code base for quite some time. I work
with git every day and am very comfortable with it.

I would like to apply as a Rookie RM. I never had the opportunity to do
release management on a project of this scale, but I'm motivated to learn.

Thanks for considering me.

Pierrick

Le mer. 27 avr. 2022, à 01 h 15, Joe Watkins krakjoe@gmail.com a écrit :

Hi all,

Applications are open for a week.

Two people will be chosen by election and a veteran will help them.

If no other veteran comes forward I will continue in that role for 8.2.

Cheers
Joe

On Tue, 26 Apr 2022, 21:21 Eric Mann via internals, <
internals@lists.php.net>
wrote:

I'm new to this mailing list as I'd previously (and very mistakenly)
assumed it was meant for existing contributors. So I've always consumed
conversations via web-based aggregators rather than directly.

My mistake.

That being said, I am very interested in being a part of this release.
I've been using PHP since ~2005 and cut my teeth on PHP4. Since then,
I've covered everything from Fortran to VB.net and C# to Ruby to Python
to Golang. Today I write a mix of Python and PHP primarily (with a
smattering of Go and a curiosity about Rust). I'm not a C guru, but in
previous roles worked with several of them and can follow my way around
a C codebase. I've frequently gone spelunking through PHP's system to
help document various methods or interfaces exposed by the standard
library as well.

I am in no way a veteran PHP RM, but I am a fairly experienced RM with
private codebases. I live and breathe in Git, love automation, and have
been accused of more than a passing fancy in security as well. Somewhere
along the line I managed to coax php[architect] into publishing my book
on the OWASP Top Ten, and they still put up with my monthly security
column as well.

In other words, I'd love to be a part of this and am more than happy to
answer any and all questions y'all want to throw my way.

~Eric Mann

From: Sergey Panteleev sergey@sergeypanteleev.com
Date: Tue, Apr 26, 2022 at 11:27 AM
Subject: [PHP-DEV] PHP 8.2 Release Manager Selection
To: Christoph M. Becker cmbecker69@gmx.de, PHP internals
internals@lists.php.net

Hey Christoph,

Do we choose one rookie for this release or two (as for 8.1)?

Also, maybe define some kind of deadline for submitting applications
and the voting phase, thoughts?

—
wbr,
Sergey Panteleev

--
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/

2 years ago by Aaron Junker — view source

unread

Hi all,

The week, where applications were open is over. And I also saw the available candidates already got mentioned on the wiki page of PHP 8.2. So I'm curious when will voting start and how long will it last?

Thanks in advance

Aaron

2 years ago by Ben Ramsey — view source

unread

Hi all,

The week, where applications were open is over. And I also saw the available candidates already got mentioned on the wiki page of PHP 8.2. So I'm curious when will voting start and how long will it last?

Thanks in advance

Aaron

Our release manager selection process doesn’t specify a timeframe during which applications should remain open, and Christoph didn’t specify any dates/times in his initial email^1. In the past, we’ve left the application period open for over a month or longer^2.

However, given the late start to this process and the impending approach of the first 8.2 alpha, we’ll speed things along a bit.

According to the Release Process RFC^3, “a week between the last call and the vote should be sufficient.”

Consider this the “last call” for volunteers.

We will close applications on 10 May and open the polls for voting for one week, with voting closing on 17 May. This will give the new RMs just under a month to prepare for the Alpha 1 release on 9 June.

Earlier, Joe tossed his name into the hat as the veteran RM “if no other veteran comes forward.” He and I have discussed that it might be a good practice to have one of the rookie RMs from the current release serve as the veteran for the next release. In this way, any new advances or changes to the process will be carried forward to the “next generation” much more smoothly. (Please note, we’re not making this a formal rule. If we want to codify this as a requirement, someone will make an RFC.)

With that in mind, I’m volunteering as the veteran RM for 8.2. This shouldn’t stop other veterans from volunteering. If that happens, we’ll vote on the veteran RM, as well as the rookie.

Best of luck, everyone!

Cheers,
Ben

2 years ago by Joe Ferguson — view source

unread

Hello Internals,

I would like to support Eric Mann's efforts as release manager. I've
followed Eric's work for several years now and have been fortunate to meet
in person at various conferences. I believe he would be an asset to the PHP
project as a release manager.

Hi all,

The week, where applications were open is over. And I also saw the
available candidates already got mentioned on the wiki page of PHP 8.2. So
I'm curious when will voting start and how long will it last?

Thanks in advance

Aaron

Our release manager selection process doesn’t specify a timeframe during
which applications should remain open, and Christoph didn’t specify any
dates/times in his initial email^1. In the past, we’ve left the
application period open for over a month or longer^2.

However, given the late start to this process and the impending approach
of the first 8.2 alpha, we’ll speed things along a bit.

According to the Release Process RFC^3, “a week between the last call
and the vote should be sufficient.”

Consider this the “last call” for volunteers.

We will close applications on 10 May and open the polls for voting for one
week, with voting closing on 17 May. This will give the new RMs just under
a month to prepare for the Alpha 1 release on 9 June.

Earlier, Joe tossed his name into the hat as the veteran RM “if no other
veteran comes forward.” He and I have discussed that it might be a good
practice to have one of the rookie RMs from the current release serve as
the veteran for the next release. In this way, any new advances or changes
to the process will be carried forward to the “next generation” much more
smoothly. (Please note, we’re not making this a formal rule. If we want to
codify this as a requirement, someone will make an RFC.)

With that in mind, I’m volunteering as the veteran RM for 8.2. This
shouldn’t stop other veterans from volunteering. If that happens, we’ll
vote on the veteran RM, as well as the rookie.

Best of luck, everyone!

Cheers,
Ben

Joe Ferguson
JoeFerguson.me
osmihelp.org

1 year ago by Ben Ramsey — view source

unread

Hi all,

The week, where applications were open is over. And I also saw the available candidates already got mentioned on the wiki page of PHP 8.2. So I'm curious when will voting start and how long will it last?

Thanks in advance

Aaron

Our release manager selection process doesn’t specify a timeframe during which applications should remain open, and Christoph didn’t specify any dates/times in his initial email^1. In the past, we’ve left the application period open for over a month or longer^2.

However, given the late start to this process and the impending approach of the first 8.2 alpha, we’ll speed things along a bit.

According to the Release Process RFC^3, “a week between the last call and the vote should be sufficient.”

Consider this the “last call” for volunteers.

We will close applications on 10 May and open the polls for voting for one week, with voting closing on 17 May. This will give the new RMs just under a month to prepare for the Alpha 1 release on 9 June.

Earlier, Joe tossed his name into the hat as the veteran RM “if no other veteran comes forward.” He and I have discussed that it might be a good practice to have one of the rookie RMs from the current release serve as the veteran for the next release. In this way, any new advances or changes to the process will be carried forward to the “next generation” much more smoothly. (Please note, we’re not making this a formal rule. If we want to codify this as a requirement, someone will make an RFC.)

With that in mind, I’m volunteering as the veteran RM for 8.2. This shouldn’t stop other veterans from volunteering. If that happens, we’ll vote on the veteran RM, as well as the rookie.

Best of luck, everyone!

Cheers,
Ben

Hi, all!

Last call was a week ago, and applications are now closed. Thank you, everyone, who applied to volunteer as an RM!

We will put together the polls and announce the vote soon, so stay tuned.

Cheers,
Ben