[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:  jorbin
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  Awaiting
Component:  General                              |  Review
 Severity:  normal                               |     Version:
 Keywords:  needs-codex dev-feedback 2nd-        |  Resolution:
  opinion                                        |     Focuses:
-------------------------------------------------+-------------------------

Comment (by alexander.rohmann):

 Replying to [comment:71 jorbin]:
 > I think that what we need to do here is not solve this for the short
 term, but come up with a long-term policy for versions of PHP that we
 support.

 Getting to the point where no PHP EOL is unsupported instead of an open-
 ended question would solve this long term. Here's an iteration of the idea
 I've shared a few times before:

 '''10,000 foot view:'''

 1. Announce that the next major WordPress release (let's say 4.6) will no
 longer support PHP 5.2
 2. For users on PHP 5.2, divert automatic updates to the 4.5.X branch for
 security fixes. This update mechanism is already in place, it just needs
 to be flagged by version number.
 3. Repeat for PHP 5.3, then 5.4 with major releases to follow.

 '''Solving:'''
 * Nobody is forced to update
 * Knowing upfront, and without being on the clock, web hosts will have
 plenty of time to update PHP
 * It's not a huge shock, as we're starting with the oldest version, and
 spreading things out over long release cycles.

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