The PHP internals mailing list thread covers the RFC for deprecations planned for PHP 8.6, compiled over the past year by multiple contributors. Each deprecation will be voted on individually, with the RFC needing to be finalized by July 13th. A notable debate emerges around whether proposals should include formal impact analyses. Juliette Reinders Folmer argues it is irresponsible to vote without impact data, while Tim Düsterhus counters that deprecations are not breaking changes and that impact analyses based on Packagist packages are inherently biased and incomplete. Rowan Tommins sides with Juliette, stating he will vote 'No' on any proposal lacking impact information. One contributor, Osama Aldemeery, shares a concrete impact analysis for the 'return-in-finally' deprecation, finding it affects only 12 places across 9 packages (~0.18% of top Composer packages), with 3 being latent bugs.
