[wp-trac] [WordPress Trac] #57345: Bump the minimum required PHP version to 7.2

[WordPress Trac]

#57345: Bump the minimum required PHP version to 7.2
-------------------------------------------------+-------------------------
 Reporter:  SergeyBiryukov                       |       Owner:  (none)
     Type:  task (blessed)                       |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests 2nd-        |     Focuses:
  opinion                                        |
-------------------------------------------------+-------------------------
Changes (by hellofromTonya):

 * milestone:  6.2 => Future Release


Comment:

 Replying to [comment:29 azaozz]:
 >don't think all the conditions are met yet. Generally the conditions are
 as follows:
 >
 > 1. The number of sites that will be "left behind" (on less than the new
 min version) have to be less than 5%, not 5% per PHP version. Currently
 that number is about 8.5% if excluding old WP sites that are on even older
 PHP versions.

 I think we can all agree that bumping the minimum supported PHP version is
 needed. But the criteria to do a bump has not yet been met. I agree with
 @azaozz. The user data < 5% (as noted) is a must-have requirement set by
 Matt. 8.5% is really close, but not yet less than 5%. Continuing to help
 users upgrade off of old versions will help to drive the numbers down.

 Once the numbers are low enough, then I also agree with these steps
 @azaozz identified, i.e. before doing the work in Core.

 > 2. Even if the above number was at 5% or below, 6.2 is far too soon to
 bump the minimum PHP version. What usually happens when WordPress
 announces PHP version bump is that hosting companies start to move WP
 sites to newer PHP versions. However that takes time. So these
 announcements should be made well ahead of the cut-off date.
 > 3. After the above conditions are met, a final decision about the cut-
 off date can be made and be approved by the project leadership.


 I also agree that this ticket is too early for 6.2 and should move to
 `Future Release`.

 > In that terms think this ticket should be milestoned to "future
 release", not 6.2.

 Moving to `Future Release` but leaving `2nd-opinion` keyword in place to
 invite more Core Committers to share their thoughts.

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