The PHP internals mailing list thread covers the RFC for deprecations planned in PHP 8.6, compiled from proposals submitted over the past year. Each deprecation will be voted on individually, with a freeze deadline of July 13th. A notable discussion emerges around the lack of impact analyses for most proposals — Juliette Reinders Folmer calls it irresponsible, while Tim Düsterhus argues that deprecations are not breaking changes and that impact analyses based on Packagist data are inherently biased and incomplete. Rowan Tommins sides with Juliette, stating he will vote 'No' on any proposal lacking impact data. One concrete example shared is the 'return-in-finally' deprecation, where an analysis of ~5000 Composer packages found only 12 affected sites across 9 packages (0.18%), with 3 being actual latent bugs.
