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

 Replying to [comment:111 jorbin]:
 > I'm really not sure what many of the comments here are about, but they
 don't seem to be about coming up with a strategy for upgrading the minimum
 version of PHP.
 I hope @jdgrimes explained reason for such impression. To me, it looks
 like people were waiting to see actual arguments and feedback from the
 core developers and it's great it happened!

 > One thing that I think predates implementing any sort of process is
 coming up with some user level educational materials about 1) What PHP
 (and for that matter, MySQL and other server technologies) are 2) Why new
 versions are important and 3) How to go about upgrading. I would love to
 see someone step up and own the creation of that matterial.
 Absolutely fair point. I propose to make it open and collaborative effort,
 perhaps using GitHub.

 If you are asking for suggested strategies and concrete ideas, here are
 mine.

 1. Start joint effort on educational materials which would be linked from
 the dashboard.
 2. Revive #23880 to improve UX. Personally, I think it would be good to
 contact guys working on [https://github.com/Yoast/whip Yoast whip package]
 to make use of their ideas and also make sure the work isn't duplicated
 without a need.
 3. When looking at PHP 5.2 (or any other PHP version) usage metrics, focus
 on last two major releases of WordPress. People running older versions
 probably just abandoned their installs.
 4. I wasn't able to find out much about WordPress release process so I
 don't know if there is any strict scheudle for releasing new major
 versions and how often it happen. For now, let me suggest three major
 releases cycle (so it results in about the one year if I'm not mistaken).
 First release to just inform people that WordPress is looking for new
 possibilities and improvements and thus they should know what the hell
 that PHP is and why running old version is bad for them. Second release to
 inform that it's last branch (in terms of software management) compatible
 with their current environment (provided with educational materials, of
 course) and third release to actually bump the requirements.
 5. Bump to PHP 5.3. When it comes to further updates strategy, I think 5%
 of versions share (across two most recent WP releases) is safe time to
 start that three-releases cycle I talked about. Probably it's still more
 tolerant than what most software does so hopefully it would fit WordPress
 philosophy of putting user first (which I absolutely agree with, to be
 clear)

 Looking forward to hear your (and others) opinion on that! Thank you for
 your efforts of finding a consensus.

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