rfc:php6

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
rfc:php6 [2014/07/22 14:38] zeevrfc:php6 [2014/07/23 13:53] – lucky numbers are no longer mentioned nikic
Line 1: Line 1:
 ====== PHP RFC: Name of Next Release of PHP ====== ====== PHP RFC: Name of Next Release of PHP ======
   * Version: 2.0   * Version: 2.0
-  * Date: 2014-07-05 (latest 2014-07-20+  * Date: 2014-07-05 (latest 2014-07-22
-  * Author: Andrea Faulds <ajf@ajf.me>, Zeev Suraski <zeev@php.net> +  * Authors: Andrea Faulds <ajf@ajf.me>, Zeev Suraski <zeev@php.net> 
-  * Status: Under Discussion+  * Status: In Voting
   * First Published at: http://wiki.php.net/rfc/php6   * First Published at: http://wiki.php.net/rfc/php6
  
Line 52: Line 52:
 We risk nothing by calling it PHP 7.  We risk confusion and negative perception if we insist on reusing 6 for a completely different project. We risk nothing by calling it PHP 7.  We risk confusion and negative perception if we insist on reusing 6 for a completely different project.
  
-Taking a risk that stands to yield absolutely no gain is a bad decision.+Taking a risk that stands to yield absolutely no reward is not good strategy.
  
  
Line 63: Line 63:
   * While many participants on the internals mailing list were involved in the original PHP 6 effort and as such are acutely aware of its existence, the larger PHP community is not. While discussing this RFC with various developers, many did not really understand why this was even a question, because they were no more than vaguely aware that there was something like PHP 6 in the past. As such wrong expectations due to confusion about the version number should be minimal.   * While many participants on the internals mailing list were involved in the original PHP 6 effort and as such are acutely aware of its existence, the larger PHP community is not. While discussing this RFC with various developers, many did not really understand why this was even a question, because they were no more than vaguely aware that there was something like PHP 6 in the past. As such wrong expectations due to confusion about the version number should be minimal.
   * While there has certainly been precedent for missing version numbers, the examples given in the previous section involve larger changes to versioning. When going from version 1.4 to 5.0 it's a clear change in the versioning scheme and not just a skipped version. The existing precedent suggests going to PHP 2016 or something equally distinct, rather than skipping a version. (No, this is not a serious suggestion.)   * While there has certainly been precedent for missing version numbers, the examples given in the previous section involve larger changes to versioning. When going from version 1.4 to 5.0 it's a clear change in the versioning scheme and not just a skipped version. The existing precedent suggests going to PHP 2016 or something equally distinct, rather than skipping a version. (No, this is not a serious suggestion.)
-  * Choosing a language version based on "lucky numbers" or other superstition seems questionable. 
- 
  
 ===== Vote ===== ===== Vote =====
Line 71: Line 69:
  
 Voting started 2014-07-20 but was cancelled. Voting started 2014-07-20 but was cancelled.
 +
 +Voting restarted 2014-07-23 afresh and ends 2014-07-30.
 +
 +<doodle title="Shall the name of PHP NEXT be PHP 6, or PHP 7?" auth="user" voteType="single" closed="false">
 +   * PHP 6
 +   * PHP 7
 +</doodle>
  
 ===== References ===== ===== References =====
rfc/php6.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1