Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130648
Precedence: list
MIME-Version: 1.0
Date: Wed, 15 Apr 2026 21:36:59 +0200
To: Derick Rethans <derick@php.net>
Cc: Ben Ramsey <ramsey@php.net>, internals@lists.php.net
Subject: Re: [PHP-DEV] [RFC] Release Manager Selection
In-Reply-To: <ec442d87-2399-7d21-cdc2-3bc6a4477455@php.net>
References: <093f97b0805b43ae640d80b9e06eb203@bastelstu.be>
 <20260328063516.0050F1A00BD@lists.php.net>
 <ec442d87-2399-7d21-cdc2-3bc6a4477455@php.net>
Message-ID: <9162648a9c24410e864bdb41f6c78625@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

I was waiting for the RM vote to end before replying here further to not 
influence the active vote.

Am 2026-03-31 12:08, schrieb Derick Rethans:
> I don't think we even should say that a "veteran RM being one of the 
> RMs
> of the *previous* PHP version". A previously active one should be fine
> too.

My proposal specifically uses the term “customary” here: For PHP 8.2, 
8.3, 8.4, and 8.6 it was a hands-on RM of the previous release who did 
the hands-off duty for the next release (PHP 8.5 was an exception to 
this pattern). I also think it makes sense for two reasons:

- It ensures that the knowledge of the hands-off RM is up to date with 
the most recent practices and workflows.
- It only extends the existing duty by one additional year, since the 
hands-off tasks can run alongside the hands-on tasks for most of the 
time.

But I agree that it is not *necessary* to strictly follow this rule, 
anyone who already did hands-on duty is qualified for hands-off duty.

Best regards
Tim Düsterhus