zlacker

PHP learned the lessons of the Python 2/3 transition and is making backwards compatibility breaks much more carefully. “fundamental breaking changes […] often” seems like an exaggeration to me.

PHP 7 made a few big and necessary changes but they generally did not affect well-written code much. Python 3 broke a lot of things without good justifications, and without a way to make your code compatible with Python 2 at the same time.

>>TazeTS+(OP)
I remember one breaking syntax change in PHP 7 a larger project was affected and it was tested with grep and fixed with sed in a matter of minutes.

There is benefit if you have the project under test and can run the build with different php versions thought. Best in parallel so you have current, next and future. It perhaps becomes the norm since the yearly release cycle but always was a requirement when supporting different php versions.