Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108415
To: PHP Development <internals@lists.php.net>
Autocrypt: addr=d.h.j.takken@freedom.nl; keydata=
 xjMEXimHTRYJKwYBBAHaRw8BAQdAzvRUI24yOGvteVk9N6VKIt425fNgg0P1rvD2WQLGP+fN
 JERpayBUYWtrZW4gPGQuaC5qLnRha2tlbkBmcmVlZG9tLm5sPsKtBBMWCAA+FiEEvtrj9qG2
 TA2YmjvLhef0X6cSlpAFAl4ph00CGwMFCQlmAYAFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
 IQkQhef0X6cSlpAWIQS+2uP2obZMDZiaO8uF5/RfpxKWkPywAQChh9Z1jSvitkT3sIipwMlk
 dnUlYY5Ue3lHBBhF6pQUOwD/XtEz/fsjvqE/GpjJhXpxNodwKjLhaUiFe9qRwwH/5QXOOARe
 KYdNEgorBgEEAZdVAQUBAQdAMNSCUI0PnOjjrFKZDAFRQzKLVDCINuFNgsXh0snmlUwDAQgH
 wpUEGBYIACYWIQS+2uP2obZMDZiaO8uF5/RfpxKWkAUCXimHTQIbDAUJCWYBgAAhCRCF5/Rf
 pxKWkBYhBL7a4/ahtkwNmJo7y4Xn9F+nEpaQEYUA/2mZ3uEN0JTRUZbxHGBMB4IhQw0cdIML
 FpFrTycqUCXCAQD5rWXomBWVD/DRHk7O3KjNsek9F1DEZgGeZ5pPmNF/Dg==
Message-ID: <7ec81bed-6e8e-93c8-c184-ddd7c9d77ec4@freedom.nl>
Date: Thu, 6 Feb 2020 15:52:41 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: PHP 7.5
From: d.h.j.takken@freedom.nl (Dik Takken)

Hi all,

Occasionally a change for PHP 8 is suggested and rejected because of it
being too disruptive compared to PHP 7.4. This is unfortunate because it
means we succeed less in seizing the opportunity to get language
improvements into the 8.x series.

In a recent thread about fixing a problem related to optional / required
parameters Gert (gertp93@gmail.com) suggested a PHP 7.5 release for
deprecations only. I like this idea as it gives us a viable migration
path for changes that currently cannot be done in 8.0.

The 7.5 release could be published when PHP 8 enters feature freeze.
Until then, deprecations warnings and notices can be accumulated in 7.5
as part of the PHP 8 development process. RFCs that target PHP 8 can
include changes to 7.5 to sketch a viable migration path.

Thoughts?

Regards,
Dik Takken