Notice, old way may still preferred in some case (at least by me). 1/ new major version of an extension Ex: php-pecl-redis5 / php-pecl-redis6 Using php-pecl-redis as package for "latest" version will imply to push new major API only in rawhide Such change (breaking BC) is not suitable for stable branches, especially for EPEL More benefits: - "dnf install php-redis" will pull the higher version - no unwanted upgrade to unwanted new API - use choice between versions 2/ new major version of an application Ex: phpunit9 / phpunit10 / phpunit11 and dependencies Same goal that 1st case, give users the choice More: new version requires newer PHP ex: phpunit11 requires PHP 8.2 So upgrading a "phpunit" package to v11 will breaks update of people using PHP 8.0/8.1 (ok, this is mostly for users of my repo) So, this is perhaps not an issue for Fedora with its short life cycle, but a real pain for Enterprise Linux. Remi -- _______________________________________________ php-devel mailing list -- php-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to php-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/php-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
