| The main problem is the PHP release schedule: https://www.php.net/supported-versions.php
If we release with PHP 7.4, the upstream security support will end sooner than security support for Debian bullseye. If we release with PHP 8.0 we will have full three years of upstream support.
There’s still month before the transition freeze and we will have time to fix the downstream users after the transition is over.
I think the transition is worth the trouble. Having official security support is important especially for PHP. Ondřej -- Ondřej Surý <ondrej@sury.org> (He/Him) On 11. 12. 2020, at 17:38, David Prévot <taffit@debian.org> wrote:
Hi Ondřej,Le Tue, Dec 08, 2020 at 09:28:38AM +0100, Ondřej Surý a écrit :I would like to transition the PHP to version 8.0;
The timing of this request makes me uneasy: php8.0 has been in Debianfor less than a week, and we are a month away from the transitionfreeze.it's not such a huge bump as it was with 5.6 -> 7.0 and
If I remember correctly, the 7.3 -> 7.4 was not a huge bump either, yetphp7.4 packages were in Debian months before the actual transitionhappen, and it took months for the updated php-defaults to actuallymigrates into testing.most of the packages that were compatible with PHP
7.4 are working just fine with PHP 8.0.
That does not match my experience as a maintainer of about a hundredpackages relying on PHP. Many upstream are currently releasing updatesto fix compatibility with PHP 8.0, and many more have not yet done so.I’m actually surprised to discover this request in the BTS without anyprior communication with teams involved in PHP related packaging.For example, PHPUnit 8 as currently available in unstable and testing isexpected to run on PHP 8 (thanks to upstream updates less than two weeksago), yet “Please note that the code coverage functionality is notavailable for PHPUnit 8.5 on PHP 8.” (from upstream changelog 8.5.12).So shipping PHPUnit 8 with PHP 8 would mean having a majorfonctionnality unavailable for the whole Bullseye life cycle. PHPUnit 9is available from experimental, yet uploading to unstable would meanhaving to deal with dozens of breakage (in the FTBFS form):https://release.debian.org/britney/pseudo-excuses-experimental.html#phpunitPHPUnit is just one example, but it seems unrealistic to ship version 9with Bullseye (I really abandonned this option months ago). Otherpackages will break (and I suspect the number of breakage will be high).This kind of disruptive change would hopefully be better suited early inthe release cycle rather than just before the beginning of the freeze.That said, it would be nice to have an updated php-default in*experimental* to help have a grasp of the possible brekages.RegardsDavid
|