Re: Next major version must be 7 (Lessons learned from the ECMAScript committee)

On 03/13/2010 08:55 AM, Keryx Web wrote: > Hi again > > Trying to drive home this message I am starting a new thread. > > Mini-summary: The next *major* edition of PHP must be 7, not 6. > > Summary: > > A. There seem to be universal agreement that the up until last week > branch of PHP called trunk was going to be PHP 6 is a dead end and not > the way into the future. (I'll call this "PHP 6.old" from now on. > > B. Instead a more incremental approach is better, according to the > consensus. (I'll call this "PHP.next".) > > C. BUT: There is a ton of articles and slides and blog posts describing > PHP 6.old on the net already. > > D. If there will be a new major edition of PHP with the version number > 6, not based on "PHP 6.old" but "PHP.next" it will take a huge amount of > time for the old resources to disappear from Google search results and > peoples minds. > > E (for ergo): The next major version of PHP must be called 7, to avoid > confusion. Could we not at least agree on this? > > This is not a technical decision. It is a pedagogic decision. > > It is not a decision about if we are going from 5.3 to 7 directly or if > there should be a 5.4 release in between. Nor is it a decision about > timetable or features. > > (And it is an appropriate slap to publishers who have put out books with > PHP 6 in their title, just for marketing purposes.) > > OK? No, not ok. We will call the next release whatever we like. People who have written books or articles about PHP 6 inferring they knew what the final state of PHP 6 would be were misguided. We never got to the point of a final feature set much less a release date. -Rasmus