-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Upgrade to PHP 8.2 #644
Comments
I also find enums (added in PHP 8.1) quite useful. |
I simulated the Fiber API here; it's where we could benefit by upgrading, where we need not test for also the-seo-framework/inc/classes/meta/factory/image.class.php Lines 612 to 639 in e44d72a
We have various functions that could benefit from the-seo-framework/inc/functions/utils.php Lines 70 to 72 in e44d72a
This could be condensed using array unpacking by string the-seo-framework/inc/classes/meta/factory/image.class.php Lines 678 to 685 in e44d72a
We're already using Some properties could benefit from being About |
See #98 and #608.
We expect TSF v5.0 to be released late 2024-- that's when most sites have hopefully upgraded to a secure PHP version–that'd be 8.2. See https://www.php.net/supported-versions.php.
Since the jump from PHP 8.0 to 8.2 is perceived as minor, we expect that most PHP 8.X users will be on 8.2 by the time we upgrade from 7.4.
Features we'd want to utilize
PHP 8.0
isset()
/method_exists()
/etc., condensing code.false/0 !== strpos()/strrpos()
, more readable code.PHP 8.1
PHP 8.2
Conclusion
The tiny list of features in 8.2 does not justify an upgrade unless we can reasonably assume most sites are upgraded.
Proposed version
Ref: https://wordpress.org/about/stats/
We'll upgrade to a version that at least 66% of sites support at our scheduled release. We previously aimed at 85%. However, since WordPress reports data from inactive sites and prevents users from updating plugins with unsupported required PHP versions, I see no issue in upgrading earlier.
TSF v5.0 will have an estimated 6-month development cycle. Hopefully, we can get started somewhere early or even before 2024.
Extension Manager's upgrade will follow soon after that.
The text was updated successfully, but these errors were encountered: