[wp-trac] [WordPress Trac] #33381: Strategize the updating of minimum PHP version.

[WordPress Trac]

#33381: Strategize the updating of minimum PHP version.
-------------------------------------------------+-------------------------
 Reporter:  alexander.rohmann                    |       Owner:
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:  maybelater
 Keywords:  needs-codex dev-feedback 2nd-        |     Focuses:
  opinion                                        |
-------------------------------------------------+-------------------------

Comment (by mbabker):

 So I'm going to "butt in" here with an outside perspective from a project
 that did a PHP bump on the same EOL PHP branch last year.  In Joomla, we
 moved from 5.3.1 to 5.3.10 with a transition period giving security
 support for the old minimum.  Yes, there were user groans about the change
 (I would suggest searching our forums if really interested), but
 surprising to me was that the most vocal groans came from those we would
 say are technically capable of managing their PHP installs.  Those folks
 worked at companies with policies or made decisions that they were only
 using the *nix LTS versions (at that point most were on 5.3.3 and the new
 LTS releases were just getting tagged), and those folks made demands that
 a version minimum shouldn't be forced but rather feature detection
 mechanisms with fallbacks or using those tests to block running the app.
 From my experience in that and observing what WordPress has done with
 hosts, the right calls are being made for the end user at the expense of a
 lot of excess baggage in not forcing an update.  Just some random food for
 thought.

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