Hey, On 17/12/2022 11:13, Pierre Schmitz wrote:
With the release to PHP 8.2 I will introduce a new set of packages to solve most of the issues with PHP updates. There are two valid requirements: On one hand people need the latest version to use its features or to develop new applications. And on the other hand users want to run third party applications that might not yet be compatible with the latest PHP runtime. I'll make the following changes to support both use cases while still keeping the rolling release model: <snip> In the end this would result in the following release schedule:
php: currently 8.1 soon 8.2 December 2023: 8.3 php-legacy: currently: 8.1 December 2023: 8.2 (upstream provides security updates till December 2024; so we have some room to postpone when issues arise.)
I don't object against providing an older PHP but why is it named php-legacy? We don't really have a policy for this, but it feels inconsistent versus the current php7, ruby2.7 package. (Ofcourse nodejs-lts-gallium is then also inconsistent but at least that is clearly named as that upstream). Greetings, Jelle