[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 alexander.rohmann):

 Ok, well at least that confirms what I mentioned earlier about
 plugin/theme developers being second class citizens. ;)


 Replying to [comment:59 Ipstenu]:
 > At this time, I feel any plan of action would be detrimental to the
 people least prepared and able to solve anything: the users.
 >
 > Change that (or have a technical/security reason to burn 5.2 in a fire)
 and I'm all in.

 We're talking about a plan that doesn't leave them in the cold. Actually,
 we're barely talking about a plan at all - which was the point of this
 ticket....

 Your assumption that "any plan of action would be detrimental" is
 shortsighted and presumes that those involved in WordPress lack the
 creative thought and wisdom to find a way to solve this in a way that
 helps move forward without alienating the community. It's a tall order,
 but not impossible. Yes, there will be fallout, but it won't be
 unmanagable.

 '''Can we please stop debating whether to change or not?''' It would be
 great if we could put some creative thought together and come up with a
 few more proposals on how to solve this longterm, '''instead of all this
 off topic debate'''.

 '''On Topic:''' Summarized from above, here are some ideas and progress we
 have so far. These are in no particular order, and represent small
 potential parts of a larger more organized plan that we're hoping to see
 implemented by someone with the authority to do so.

 * Detect PHP 5.2 and prevent automatic updates to a major release. Users
 will still get security updates.
 * Show a notice to users on PHP 5.2 letting them know that they can't
 update to a major release, and have them request their host to update PHP,
 or move them to a server that is more capable.
 * We have interest and willingness by those above to work directly with
 hosts, and users.
 * Do this over a period of time long enough that hosts can upgrade PHP, or
 relocate users.

 With these actions, "users" will be pretty much in the clear. Hosts will
 have it the hardest, but we can give them time (instead of letting them
 take it from us) by having some timeframes announced.

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