Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127105
Precedence: bulk
MIME-Version: 1.0
Date: Sun, 13 Apr 2025 23:07:07 +0200
Message-ID: <CAPTD5yFaQL58uJ3Focij9HKT-u-70fTDdzBWsqxpAru2YRZaqQ@mail.gmail.com>
Subject: [PHP-DEV] [RFC] [Discussion] Minor version compatibility
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001ab77c0632af52db"
From: jorg.sowa@gmail.com (Jorg Sowa)

--0000000000001ab77c0632af52db
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thank you all for the feedback on the topic of BC breaks in argument
validation https://news-web.php.net/php.internals/126706

I have collected all concerns, prepared an RFC for this change, and I'm
opening discussion on its content:
https://wiki.php.net/rfc/minor-version-compatibility

Since this touches on the broader topic of release policy and BC
expectations, I=E2=80=99d also like to open the door for related improvemen=
ts.
Rowan raised several valid points that highlight the need for clearer
communication and expectations around minor version changes. If the
community feels it's appropriate, I=E2=80=99m happy to include these sugges=
tions in
the voting. The more clearly BC policy is defined, the less time we=E2=80=
=99ll need
to spend on debating individual cases in the future.

Rowan=E2=80=99s suggestions included examples like:

Maybe we could work on some criteria that could be applied (and publicised
to users) about what is and isn't allowed in minor versions.
For instance:

   -

   Code that already causes fatal behaviour might cause different fatal
   behaviour (e.g. throwing an Error instead of raising an E_ERROR)
   -

   Code that directly violates documented types might start throwing
   TypeError
   -

   Code that previously returned null for invalid inputs might start
   throwing ValueError

Kind regards,
Jorg

--0000000000001ab77c0632af52db
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Thank you all for the feedback on the topic of B=
C breaks in argument validation <a href=3D"https://news-web.php.net/php.int=
ernals/126706">https://news-web.php.net/php.internals/126706</a><br><br></d=
iv>I have collected all concerns, prepared an RFC for this change, and I=
9;m opening discussion on its content: <a href=3D"https://wiki.php.net/rfc/=
minor-version-compatibility">https://wiki.php.net/rfc/minor-version-compati=
bility</a><br><br></div>Since this touches on the broader topic of release =
policy and BC expectations, I=E2=80=99d also like to open the door for rela=
ted improvements. Rowan raised several valid points that highlight the need=
 for clearer communication and expectations around minor version changes. I=
f the community feels it&#39;s appropriate, I=E2=80=99m happy to include th=
ese suggestions in the voting. The more clearly BC policy is defined, the l=
ess time we=E2=80=99ll need to spend on debating individual cases in the fu=
ture.<p class=3D"gmail-">Rowan=E2=80=99s suggestions included examples like=
:</p>
<blockquote>
<p class=3D"gmail-">Maybe we could work on some criteria that could be appl=
ied (and publicised to users) about what is and isn&#39;t allowed in minor =
versions.<br>
For instance:</p>
<ul><li class=3D"gmail-">
<p class=3D"gmail-">Code that already causes fatal behaviour might cause di=
fferent fatal behaviour (e.g. throwing an <code>Error</code> instead of rai=
sing an <code>E_ERROR</code>)</p>
</li><li class=3D"gmail-">
<p class=3D"gmail-">Code that directly violates documented types might star=
t throwing <code>TypeError</code></p>
</li><li class=3D"gmail-">
<p class=3D"gmail-">Code that previously returned <code>null</code> for inv=
alid inputs might start throwing <code>ValueError</code></p></li></ul></blo=
ckquote><div>Kind regards,<br></div><div>Jorg</div></div>

--0000000000001ab77c0632af52db--