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 On Wed, Mar 1, 2023 at 8:21 PM Sergey Panteleev <ser...@php.net> wrote: > 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 >
