-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dev: drop PHP 8.0 support with CI 4.4 #7320
Comments
The problem is the share of PHP 7.4. |
Yes I'm totally fine with that, for people who can't run CI 4.4 with PHP 7.4 anymore it would be not a problem to directly switch to PHP 8.1 / 8.2 instead of PHP 8.0.
My opinion is that sometimes forcing people to do the right thing is ok. E.g., forcing them to use a secure PHP version when they want to upgrade to CI 4.4 |
I know your opinion. |
big changes are the harbinger of growth... growth is good :) |
I posted on the forum. |
PHPUnit 10 requires PHP 8.1 or PHP 8.2. |
I would like to drop 8.0 in CI 4.5. |
laminas-escaper 2.13 requires PHP 8.1 or later. |
I sent PR #8042 |
PHP 8.0 support will be dropped in 4.5. |
PHP 8.0 will reach the end of life on 28 Nov 2022.
https://www.php.net/supported-versions.php
Relating to #6921 : guessing that this won't be CI 4.3 thing, so we are already at a breaking change then.
Whilst at it, drop PHP 8.0 as well, since it is already in its security-support-only phase (which itself ends in a few months 26 Nov 2023) and migration to at least PHP 8.1 should be in the process already.
This allows simplifying code using new features, at least for CI 4.4.
PHP 8.0 installation percentages are already dropping their share already, since people are upgrading to newer versions quicker than back in the day.
https://packagist.org/packages/codeigniter4/framework/php-stats
Using up energy supporting nearly EOL Versions in a "new PHP world" which is moving along way faster is a waste of energy in my opinion. It kinda feels like parts of the CI Community have not yet realized, that the "good old days" of having PHP 5.6 maintained for many years are over and moving along is the new normal.
The text was updated successfully, but these errors were encountered: