[wp-trac] [WordPress Trac] #40934: Allow PHP version requirements for plugins & themes

[WordPress Trac]

#40934: Allow PHP version requirements for plugins & themes
----------------------------+------------------
 Reporter:  joostdevalk     |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  4.9
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  dev-feedback    |     Focuses:
----------------------------+------------------

Comment (by johnbillion):

 I'd like to see a bit of a stronger argument put forward for a PHP version
 constraint. Not because I am against it (I'm not), but because it's
 important that we qualify time and effort spent on it and fully consider
 the impact on end users.

 WordPress traditionally avoids (to a significant degree in some cases)
 exposing the end user to concerns regarding things such as PHP version,
 PHP extensions, server requirements, etc. It takes this to the extreme in
 some cases, providing shims when certain extensions aren't available (the
 `mb_*()` functions), and running with very low requirements (PHP 5.2).

 Maybe this needs to change, or maybe this is foundational to WordPress and
 the reason for its success. Maybe it's less relevant or less important now
 than it has been over the last 14 years. Maybe not, maybe partly. This
 commitment to minimal requirements and backwards compatibility needs to be
 considered.

 If we are going to consider exposing the user to a PHP version constraint,
 it's important to qualify it with the benefits that it provides. In a
 world of microservices, packages, and dependency management, this is
 routine stuff, but WordPress doesn't operate in this world. I'd like to
 see a document put together which answers:

 * What are the ''real'' benefits to plugin and theme authors of a PHP
 version constraint mechanism?
 * What problems are caused by lack thereof?
 * What are the benefits, if any, to end users?
 * What are the benefits, if any, to WordPress core or the wider WordPress
 ecosystem?

 The answers will all be subjective of course, but they'll help guide us
 with regard to prioritisation and implementation. This may seem like
 overthinking things, but supporting a PHP version constraint for plugins
 and themes introduces a fundamental change to the way WordPress is used.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/40934#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform