[wp-trac] [WordPress Trac] #33381: Strategize the updating of minimum PHP version.
WordPress Trac
noreply at wordpress.org
Sun Aug 16 01:58:48 UTC 2015
#33381: Strategize the updating of minimum PHP version.
-------------------------------+------------------------------
Reporter: alexander.rohmann | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: General | Version: trunk
Severity: normal | Resolution:
Keywords: | Focuses:
-------------------------------+------------------------------
Comment (by alexander.rohmann):
> What WordPress can and must do is to to scan the plugin/theme
directories for plugins using things that will break when running PHP 5.5
and later. So they can show to the outside that nothing can break when
moving to the latest PHP version. I already have seen enough breakage that
this can become a serious issue.
Great point. I agree that would be an important step on the WordPress
side.
> Setting the date is something that needs to be done together with host.
WordPress isn't really a big party in this. People can believe that
WordPress can push them but they can't. They can use
https://wordpress.org/hosting/ to push ("blackmail") hosts but that only
work for a few of them. Weirdly to say but WordPress is to small for it.
If there is a good way for hosts to tackle their increase in support
(fixing sites) then making the push will become easier. Depending on the
host this can be really tricky since you probably do need some development
skills.
My fear is that there are so many parties involved with nothing to gain
that no consensus will be made. I don't see how it's unfair or blackmail
if: 1. They have irresponsibly allowed their systems to decay. 2. We're
talking about an extended timeframe.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/33381#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list