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