Re: Asymmetric visibility is a BC break
| From: | AllenJB | Date: | Mon, 14 Oct 2024 10:17:16 +0000 |
| Subject: | Re: Asymmetric visibility is a BC break | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-125799@lists.php.net to get a copy of this message | ||
On 14/10/2024 10:03, Bilge wrote:
On 14/10/2024 02:51, Valentin Udaltsov wrote:Hi, Bilge! I think that PHP should then clearly explain what is a BC break and what isn't on a separate php.net page. And even explain what php version constraints are safe for Composer libraries. Some languages have such a document: -https://go.dev/doc/go1compat -https://peps.python.org/pep-0387/Absolutely! After some 16 years using PHP, I only recently became aware BC breaks are acceptable in minor versions. For anyone spending significant time in open source, I think there is a tendency to become semver-minded and naturally assume PHP follows the same; it does not. Cheers, Bilge For reference, current policy on BC-breaks is here: https://github.com/php/policies/blob/main/release-process.rst