On 3/27/26 13:15, Tim Düsterhus wrote:
Hiplease find the following RFC that is intended to clarify the “Release Manager Selection” policy for future PHP versions:https://wiki.php.net/rfc/release_manager_selection_policyIt is written in response to this email in the PHP 8.6 RM selection thread that pointed out possible ambiguity with regard to who is allowed to apply as a RM and as to how to interpret the results of the vote: https://news-web.php.net/php.internals/130402Best regards Tim Düsterhus
I'm not sure I like the notion or language of "hands-off" vs. "hands-on" release managers. What we've effectively practiced since at least PHP 8.1 is this:
1. At least 3 RMs per release 2. At least 1 of the RMs MUST be a veteran to advise the others 3. At least 2 of the RMs MUST be active during their tenureThe RMs themselves decide how they want to organize their schedules. I don't think the policy needs to be much more rigid than this.
It's okay for more than 1 RM to be a veteran, provided at least one of the 3 RMs is a veteran.
I think it's okay for someone to be an RM on up to 2 actively supported versions of PHP at the same time. They'll need to work together with their fellow RMs to ensure their duties are adequately covered, but I disagree with designating whether anyone is "hands-on" or "hands-off."
Cheers, Ben
OpenPGP_signature.asc
Description: OpenPGP digital signature
