[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 jdgrimes):

 Speaking of WordPress philosophies, I've had a thought on this that I've
 declined to voice up until now, but here it goes. One of WordPress's
 development philosophies is the 80% rule. Any feature that doesn't benefit
 80% of users doesn't belong in core. While that is about user-facing
 features, can't we at least agree that the same type of logic really has
 to be applied here at some point? Right now we are holding the entirety of
 WordPress core hostage to 5% of users. Putting in so much effort to please
 a small number of users is silly, which is why the 80% rule exists. I
 think that if the average user knew that WordPress was putting a large
 amount of effort into not breaking 3% of user's sites, rather than
 building new features or fixing real bugs, they would be disgusted. Sure,
 everyone is pleased that we want the best for users, but building
 WordPress 20.5 to run on a PHP version that 5 sites are still hanging onto
 is ridiculous. Obviously, that isn't something that anybody is suggesting
 should happen here. The question this ticket is trying to resolve though,
 is what exactly ''is'' going to happen? And until there is an actual
 discussion where the core devs are helping develop a strategy instead of
 saying  "not yet", many developers are going to remain frustrated. As
 pointed out above, if WordPress doesn't lead on this, forcing plugin
 authors to take the initiative, the developer community is going to
 fragment, and as a result UX is going to be degraded.

 So OK, maybe we're not going to come up with a 95% rule for PHP versions.
 Maybe we want to be more pragmatic here (and that's probably good). But it
 is very frustrating when there is no end in sight, when there doesn't even
 appear to be any desire to even begin the process of preparing to prepare
 core for this. For all we know, WordPress 20.5 ''will'' still support PHP
 5.2, because there seem to be no plans whatsoever to strategize actually
 updating the PHP version someday. It is almost as if we are hoping to
 ignore the problem and then it will go away. We know that isn't the
 intention, and that the goal is doing what is best for users. But we'd
 like some of the core devs to reconsider whether this is still the best
 thing for users at this point, or at what point continuing to support
 outdated PHP versions is no longer going to be the best thing for users.
 At some point it isn't anymore. I think everyone agrees on that. Somehow
 though, we're able to disagree about whether we should talk about when
 that point is, and how to prepare for it.

 Huh, when put that way, it is actually kind of humorous. :-)

 Actually though, after considering the recent replies to this ticket, a
 sort of strategy has been outlined, though it needs some polish:

 - Wait.
 - Let plugins do the legwork.
 - At some point, as yet undetermined, up core's requirement.

 Others have already objected to different parts of this strategy, so I
 won't bother with that. I will say though, that if this is the way that we
 are going to go, then WordPress should encourage it by reducing pain for
 users as plugins start becoming incompatible. Otherwise this is pretty
 certainly ''not'' the best experience for users. #23880 would seem to be a
 must.

 Also, even given that, it still doesn't invalidate the point of this
 ticket. WordPress core will still need to prepare to update, and still
 need to come up with some idea of when it will do that (IMO).

 Finally, I'd like to echo @fightthecurrent's reply to @johnbillion: we
 should also be strategizing when and how to EOL WordPress 3.7. The
 80%-rule type logic applies there too. Backporting indefinitely risks
 bringing the development of new features to a complete halt. Not in the
 best interest of users. At some point we have to stop rewarding
 irresponsible users at the expense of responsible ones. It is just wrong.
 OK, they are really just ignorant. Then educate them. If they don't take
 action, then they are definitely irresponsible. Being irresponsible means
 that bad things happen sometimes. Like your site getting hacked. As others
 have said, it is called life. This isn't being callous, it is seeing a
 problem that will eventually place a drag on the entire project, and
 taking the initiative to inform the affected users so they can fix it.

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