Silverstripe-framework: RFC: SilverStripe 5 should require PHP 7.2 minimum

Created on 27 Feb 2019  路  10Comments  路  Source: silverstripe/silverstripe-framework

Affected Version

5.x

Description

PHP dropped support for PHP 7.1 on December 1, 2018 (reference). We should bump the minimum required version in SilverStripe 5.x to PHP 7.2, and increase PHPUnit to ^8 (related: use PHPUnit ^7 in SilverStripe 5.x (already done)).


Not sure if this needs an RFC or whether this falls into the default PHP version support commitments for us releasing new versions, but since it's a while off I figure it's a given that we will implement this policy for SS5.

affectv5 changminor efforeasy impacmedium rfaccepted

All 10 comments

Makes sense to me; that still works with SS3.7, even. Depending on timing we might also make it PHP 7.3 (which also works with SS3.7)

Is there a scenario where SS5 wouldn't support an actively supported version of PHP? e.g.: Let's say PHP 7.5 is release and PHP 7.3 is still supported, but we decide that you need at least PHP7.4 to run SS5.

I think it might make sense to do that at the beginning of an SS5 release, as we would be more reticent about dropping releases in 5.x minor releases. So we might release SS5 as 7.4+ assuming that 7.4 is available when it's released, even if 7.2 and 7.3 haven't yet EOLed.

I think the main thing is that there is at least 1 version of PHP that runs both SS4 and SS5.

Didn't we recently decide to drop support for 5.x in a minor release? Why can't we say "require 7.2 minimum" in the next minor release?

We're dropping PHP versions 6 months after they EOL, it's not a free-for-all.

Moving to accepted since we've already agreed to do this in SilverStripe 4.x minor releases (removing support for unsupported PHP versions 6 months after their EOL.

OK I'm gonna do a small PR to master so we can close this out.

Actually I'm gonna:

  • Update 4 to drop 5.6 and 7.0
  • Merge 4 into master
  • Update master to drop 7.1

@sminnee thanks for doing this in framework with #9010. Remaining tasks to update in all core modules and recipes. We don't have SilverStripe 5.x branches for any supported modules yet, so we can ignore them for now.

I'm going to close this as done, since it's in framework already

Was this page helpful?
0 / 5 - 0 ratings