Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129506
Precedence: list
MIME-Version: 1.0
References: <CAEKnhAEchz+Uovurn9yP7Dfu1p5yK2mihJSQLJLkmX721Z152A@mail.gmail.com>
 <CAEKnhAFig86RdM0tyzPQNAANSjZ2M2RsC-7qPLkYN2gS04O6og@mail.gmail.com>
 <CAEKnhAF2LjNUNKiF701NZoU+MiBDtS+tnOQYcBgBBE7vTJF0Sg@mail.gmail.com>
 <07d7e38a-afab-43f0-9532-3427f1a71526@app.fastmail.com> <40a322a2-e62f-368a-16bc-962d25e75353@php.net>
In-Reply-To: <40a322a2-e62f-368a-16bc-962d25e75353@php.net>
Date: Tue, 2 Dec 2025 12:31:11 +0100
Message-ID: <CAEKnhAFao=h5Hg8ZdwCAi5SVcXG34Tx-tiRDJBKhM2ZfKufQBg@mail.gmail.com>
Subject: Re: [PHP-DEV] Re: [RFC][Discussion] Policy release process update
To: Derick Rethans <derick@php.net>
Cc: Rob Landers <rob@bottled.codes>, internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000006ec33d0644f66f58"
From: bukka@php.net (Jakub Zelenka)

--0000000000006ec33d0644f66f58
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 1, 2025 at 7:18=E2=80=AFPM Derick Rethans <derick@php.net> wrot=
e:

> On Sat, 29 Nov 2025, Rob Landers wrote:
>
> > On Sat, Nov 29, 2025, at 12:28, Jakub Zelenka wrote:
> > >
> > > The last time I sent this, there were some comments and I did
> > > another update so I delayed the vote.
> > >
> > > So this is another heads up that I plan to open voting tomorrow.
> > > This time it should be for real. :)
> >
> > > Extensions support MAY be ended (moved to PECL).
> >
> > Is "moving to PECL" still a thing? Or should this be PIE? Or just
> > remove the destination clarification?
>
> I'd say the "(moved to PECL)" can probably be just dropped.
>
>
We haven't officially announced stopping updates to PECL. Also we haven't
discussed what to do in such case with dropped extensions - e.g. if we
should still move it to the php org and just use pie there. I agree that we
should update it in the future but this RFC just didn't touch it as it
wasn't clear what to do here. Note that this is not introduced by this RFC
as the "moved to PECL" is already in the current policy.

Kind regards,

Jakub

--0000000000006ec33d0644f66f58
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Dec 1, 2025 at 7:18=E2=80=AFPM De=
rick Rethans &lt;<a href=3D"mailto:derick@php.net">derick@php.net</a>&gt; w=
rote:</div><div class=3D"gmail_quote gmail_quote_container"><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">On Sat, 29 Nov 2025, Rob Landers wrote:<=
br>
<br>
&gt; On Sat, Nov 29, 2025, at 12:28, Jakub Zelenka wrote:<br>
&gt; &gt; <br>
&gt; &gt; The last time I sent this, there were some comments and I did <br=
>
&gt; &gt; another update so I delayed the vote.<br>
&gt; &gt; <br>
&gt; &gt; So this is another heads up that I plan to open voting tomorrow. =
<br>
&gt; &gt; This time it should be for real. :)<br>
&gt; <br>
&gt; &gt; Extensions support MAY be ended (moved to PECL).<br>
&gt; <br>
&gt; Is &quot;moving to PECL&quot; still a thing? Or should this be PIE? Or=
 just <br>
&gt; remove the destination clarification?<br>
<br>
I&#39;d say the &quot;(moved to PECL)&quot; can probably be just dropped.<b=
r><br></blockquote><div><br></div><div>We haven&#39;t officially announced =
stopping updates to PECL. Also we haven&#39;t discussed what to do in such =
case with dropped extensions - e.g. if we should still move it to the php o=
rg and just use pie there. I agree that we should update it in the future b=
ut this RFC just didn&#39;t touch it as it wasn&#39;t clear what to do here=
. Note that this is not introduced by this RFC as the &quot;moved to PECL&q=
uot; is already in the current policy.</div><div><br></div><div>Kind regard=
s,</div><div><br></div><div>Jakub</div></div></div>

--0000000000006ec33d0644f66f58--