Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130412
Precedence: list
MIME-Version: 1.0
References: <IAwbcf08vnG_-P0w_xZlEdpz9whoLg_QpxRi0t1VCIfcR9cXE2TrE7-EVJvd0rlezoBh4PyT_Vw6dUpX4qv_ApA1GsDxTUlOunN9CQebYJA=@gpb.moe>
 <5791904e-343f-4125-aa58-93ea43adcc84@beccati.com>
In-Reply-To: <5791904e-343f-4125-aa58-93ea43adcc84@beccati.com>
Date: Sun, 22 Mar 2026 13:24:26 +0100
Message-ID: <CADyq6s+RhQ2M5ge20D4KCYhB_1cCss4Rv1WVwj3G0SRxsQmLxA@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [VOTE] Exempt input type and value validation
 from BC Break policy
To: Matteo Beccati <php@beccati.com>
Cc: PHP internals <internals@lists.php.net>, "Gina P. Banyard" <internals@gpb.moe>
Content-Type: multipart/alternative; boundary="0000000000007be025064d9c00aa"
From: ocramius@gmail.com (Marco Pivetta)

--0000000000007be025064d9c00aa
Content-Type: text/plain; charset="UTF-8"

Hey Gina,

On Sat, 21 Mar 2026 at 20:26, Matteo Beccati <php@beccati.com> wrote:

> Hi Gina,
>
> Il 21/03/2026 12:22, Gina P. Banyard ha scritto:
> > Hello internals,
> >
> > With a small delay due to unexpected circumstances I've started the vote
> on the "Exempt input type and value validation from BC Break policy" policy
> RFC.
> > It will run from today the 2026-03-21 until the 2026-04-04 at 12:00 UTC.
> >
> > The RFC can be found at the following link:
> https://wiki.php.net/rfc/policy-exempt-type-value-error-bc-policy
>
> I know the intention is good, but my fear is that the burden on third
> party OSS developers could potentially be unbearable. That's the reason
> I voted no.
>
>
> Cheers
> --
> Matteo Beccati
>

I'm having thoughts similar to Matteo's here, **but** since this is about
restricting the amount of acceptable input (for correctness and security
reasons), I think it balances out the risk, and I voted Yes.

Marco Pivetta

https://mastodon.social/@ocramius

https://ocramius.github.io/

--0000000000007be025064d9c00aa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>Hey Gina,</div></div><br><div class=
=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr=
">On Sat, 21 Mar 2026 at 20:26, Matteo Beccati &lt;<a href=3D"mailto:php@be=
ccati.com">php@beccati.com</a>&gt; wrote:<br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex">Hi Gina,<br>
<br>
Il 21/03/2026 12:22, Gina P. Banyard ha scritto:<br>
&gt; Hello internals,<br>
&gt; <br>
&gt; With a small delay due to unexpected circumstances I&#39;ve started th=
e vote on the &quot;Exempt input type and value validation from BC Break po=
licy&quot; policy RFC.<br>
&gt; It will run from today the 2026-03-21 until the 2026-04-04 at 12:00 UT=
C.<br>
&gt; <br>
&gt; The RFC can be found at the following link: <a href=3D"https://wiki.ph=
p.net/rfc/policy-exempt-type-value-error-bc-policy" rel=3D"noreferrer" targ=
et=3D"_blank">https://wiki.php.net/rfc/policy-exempt-type-value-error-bc-po=
licy</a><br>
<br>
I know the intention is good, but my fear is that the burden on third <br>
party OSS developers could potentially be unbearable. That&#39;s the reason=
 <br>
I voted no.<br>
<br>
<br>
Cheers<br>
-- <br>
Matteo Beccati<br></blockquote><div><br></div><div>I&#39;m having thoughts =
similar to Matteo&#39;s here, **but** since this is about restricting the a=
mount of acceptable input (for correctness and security reasons), I think i=
t balances out the risk, and I voted Yes.=C2=A0</div><div><br></div><div><d=
iv></div><div><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">M=
arco Pivetta <br><br><a href=3D"https://mastodon.social/@ocramius" target=
=3D"_blank">https://mastodon.social/@ocramius</a><br><br><a href=3D"https:/=
/ocramius.github.io/" target=3D"_blank">https://ocramius.github.io/</a></di=
v></div></div>=C2=A0</div></div></div>

--0000000000007be025064d9c00aa--