Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126960
Precedence: bulk
MIME-Version: 1.0
References: <88601180-801F-454E-A8EA-BD9500103DB1@cmpct.info>
In-Reply-To: <88601180-801F-454E-A8EA-BD9500103DB1@cmpct.info>
Date: Wed, 26 Mar 2025 12:13:26 -0700
Message-ID: <CALaXqqQ0jRZDD17BKwDXnczimG2mXdLPPnhYybHrEoecBqYwZQ@mail.gmail.com>
Subject: Re: [PHP-DEV] Release Managers for PHP 8.5
To: Calvin Buckley <calvin@cmpct.info>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000fe7a7f063143a31b"
From: daniel.e.scherzer@gmail.com (Daniel Scherzer)

--000000000000fe7a7f063143a31b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 26, 2025 at 12:10=E2=80=AFPM Calvin Buckley <calvin@cmpct.info>=
 wrote:

> Hi all,
>
> It's time to start the process of finding and electing RMs for the next
> minor PHP release.
>
>
I'd like to also throw my hat in the ring. I've been contributing for a
while now, and recently got VCS access/karma.


>
> Candidates should have a reasonable knowledge of internals, be confident
> about merging pull requests without breaking backward compatibility, doin=
g
> 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. Ideally, at least one of candidat=
e
> should be a core developer that can assess more technical PR's. Other
> candidates do not necessarily need to have deep knowledge of internals bu=
t
> should understand above mentioned points.
>
>
I believe I can satisfy the "core developer" candidate requirement.

-Daniel

--000000000000fe7a7f063143a31b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Mar 26, 2025 at 12:10=E2=80=AFPM =
Calvin Buckley &lt;<a href=3D"mailto:calvin@cmpct.info">calvin@cmpct.info</=
a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_container"><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
It&#39;s time to start the process of finding and electing RMs for the next=
<br>
minor PHP release.<br>
<br></blockquote><div><br></div><div>I&#39;d like to also throw my hat in t=
he ring. I&#39;ve been contributing for a while now, and recently got VCS a=
ccess/karma.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
<br>
Candidates should have a reasonable knowledge of internals, be confident<br=
>
about merging pull requests without breaking backward compatibility, doing<=
br>
triage for bugs, liaising with previous release managers, and generally<br>
getting the branch in good shape, as these are among the activities you<br>
will be undertaking as release manager. Ideally, at least one of candidate<=
br>
should be a core developer that can assess more technical PR&#39;s. Other<b=
r>
candidates do not necessarily need to have deep knowledge of internals but<=
br>
should understand above mentioned points.<br><br></blockquote><div><br></di=
v><div>I believe I can satisfy the &quot;core developer&quot; candidate req=
uirement.</div><div><br></div><div>-Daniel</div><div>=C2=A0</div></div></di=
v>

--000000000000fe7a7f063143a31b--