You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As proposed at #194 (comment) - PHP 5.6 has been unsupported for a while now, though that doesn't mean that people immediately upgrade.
If we do want to drop PHP 5.6 then the sooner the better. One reason why: if PHP version bumps happen after a released version then we probably need to make sure people on PHP 5.6 can't upgrade and break their site.
For reference, ClassicPress will be keeping support for PHP 5.6 throughout the 1.x release series, and when we prompt people to upgrade to 2.x we'll block the upgrade unless they meet the new minimum PHP version requirement (exact version TBD).
The text was updated successfully, but these errors were encountered:
According to https://w3techs.com/technologies/details/pl-php, as of today (22nd Jan 2020) more than 50% of websites are still on PHP5.x. So I think it a good idea that we do have a grace period of several months where we prompt people to update.
As proposed at #194 (comment) - PHP 5.6 has been unsupported for a while now, though that doesn't mean that people immediately upgrade.
If we do want to drop PHP 5.6 then the sooner the better. One reason why: if PHP version bumps happen after a released version then we probably need to make sure people on PHP 5.6 can't upgrade and break their site.
For reference, ClassicPress will be keeping support for PHP 5.6 throughout the 1.x release series, and when we prompt people to upgrade to 2.x we'll block the upgrade unless they meet the new minimum PHP version requirement (exact version TBD).
The text was updated successfully, but these errors were encountered: