Problem/Motivation
PHP 7 provides widely recognized significant performance benefits. We also need to do our part to make sure hosts don't get complacent. Drupal was a leader in the successful GoPHP5 movement which brought PHP hosts, and thus development, into the 21st century, a mere 10 years late. With WordPress, a laggard in the PHP5 movement, now stepping up and strongly recommending PHP version 7, it's time for Drupal to do the same, as Rachel Lawson tweeted.
One year ago in #2524432: Suggest PHP 5.6 as the recommended version Crell wrote "I fully expect that in a year we'll want to tell people to use PHP 7". That expectation should be realized! And if we don't at least recommend PHP 7, that issue, and our development, will be held up on PHP 5.5.9 forever.
And of course, Drupal 8 is, and has been, PHP7-ready: #2454439: [META] Support PHP 7
Proposed resolution
Update the text on the system requirements pages:
* https://www.drupal.org/docs/7/system-requirements/overview
* https://www.drupal.org/docs/7/system-requirements/php#8
For example:
"Drupal 8: PHP 7 or higher recommended. PHP 5.5.9 or higher required."
This separates out (and supersedes) step one of #2524432: Suggest PHP 5.6 as the recommended version. Refrained from hijacking that entire ticket as documentation can lead information notices from Drupal itself.
Comments
Comment #2
mlncn commentedComment #3
damienmckenna+1 for doing this. FYI I believe "PHP 7" is the official tag.
Comment #4
mlncn commentedMeant to mention recommending (rather than requiring) PHP 7 had a +1 from catch and others in #2605226: Require PHP 7 for Drupal 8.2
Comment #5
cilefen commentedComment #6
Crell commentedOn behalf of Platform.sh, +1! We're already defaulting all Drupal 8 sites to PHP 7.
Comment #7
David_Rothstein commentedIs this a duplicate of #2670966: Warn users of old PHP versions?
Comment #8
David_Rothstein commentedSorry, I missed this part:
and also managed to misread "System Requirements" (a documentation page title) as "system_requirements" (a function name) when I looked at the issue title :)
So this is not a duplicate, but it is related.
And seems worth doing - would like to do it for Drupal 7 too, although I'm not sure if contrib module support is quite good enough yet.
Comment #9
David_Rothstein commentedEveryone seems to be in agreement above, and I can't think of a reason not to do it for Drupal 8 - marking RTBC.
Comment #10
alexpottI think we should only do this once we support 7.1 which we're not quite ready for :(
The two blockers ATM are:
Both of these are quite sad because they are API breaking and seem extreme for minor versions but I guess this is the new normal for PHP rapidly iterating.
Also if we're going to do this should we introduce a recommendation in system requirements?
Comment #11
catchWe already have issues open for system requirements, I think it's fine to do them separately.
Let's explicitly mark this postponed on green branch tests for PHP 7.1.
Comment #12
MixologicPS. We added 7.1 to drupalci today.
Comment #15
andypostTime has come
Comment #18
pasqualleFor D8 php7 is already the recommended version https://www.drupal.org/docs/8/system-requirements/php-requirements
For D7 it is still php5 https://www.drupal.org/docs/7/system-requirements/overview
Comment #19
pasqualleactually
"5.4 or higher recommended" here:
https://www.drupal.org/docs/7/system-requirements/overview
The minimum recommended PHP version for Drupal 7 is PHP 7.1.x" here:
https://www.drupal.org/docs/7/system-requirements/php-requirements
please someone with access update the first page..
Comment #20
pfrenssenI updated the page.
Comment #21
pasqualleDo you know what is the reason that for Drupal 8 the recommended minimum is PHP7.2 and for Drupal 7 the recommended minimum is PHP7.1? Is it related to how long the current release is supported?
Comment #22
hansfn commentedThe reason that PHP 7.1 was recommended for Drupal 7, was that 7.2 wasn't supported before recently - see release notes for version 7.61. I'll update to 7.2
on both pagesnow.