On 06.07.2025 at 19:16, Tim Düsterhus wrote: > Nevertheless I found it important to point out that the deprecation > itself is not a breaking change, since it is a common theme that folks > incorrectly claim that "PHP X.Y broke my code", when it's just some > deprecation messages being emitted. The deprecation allows you to fix > the issue at hand at a pace you are comfortable with. As an example, if > the code in question is in the process of being replaced anyways, then > you don't need to do anything.
The RFC at hand states: | The RFC proposes to deprecate the listed functionality in PHP 8.5 and | remove it in PHP 9 (except where otherwise noted). That *might* give users only a year to fix the deprecated features, what might not match everybody's pace, though. It seems to be prudent to reduce the number of deprecations for the ultimate (and maybe the penultimate) minor version prior to a major release. Of course, that would require us to plan ahead. :| Christoph M. Becker
