On Wed, Apr 2, 2014 at 9:26 PM, Adam Jon Richardson <[email protected]>wrote:
> On Wed, Apr 2, 2014 at 9:51 PM, Kris Craig <[email protected]> wrote:
> > We shouldn't skip an entire version increment just because a few authors
> > screwed-up. I don't know a single person who refers to any part of the
> 5.x
> > branch as PHP 6, nor have I heard a single developer complain that there
> > will be confusion when PHP 6 is released. Skipping the version increment
> > would be a solution in search of a problem and would only serve to cause
> > more confusion.
>
> Getting back to your points:
>
> - You said "a few authors screwed-up." I think we can both agree that
> there are many websites that have information about the now-defunct
> branch of PHP 6. Try revising the search to "php 6" + unicode,
> filtering out results based on url, etc. Now, you may go on to say
> that the existence of this information shouldn't be a reason to
> abandon the naming convention. Perhaps. But, I would confidently argue
> that the number of conflicting resources will not be "few."
>
Well now we're arguing semantics. Seeing as how you have to include these
filters and the results only make-up a tiny fraction of the total--
combined with the fact that those results are all from more than half a
decade ago-- I think the word "few" is generous.
>
> - You said you've not hear a single developer complain that there will
> be confusion. I believe you've heard a few on this very list :)
>
Yes, and only on this very list. Nowhere else. OP mentioned it being a
hot topic at conferences and I'm just saying that that has not been my
experience at all. In fact, this is the first I've heard anyone complain
of the coming PHP 6 release somehow being confused with 5.x because of a
few mistitled books from the previous decade. I certainly don't think it's
worth all the confusion that would result from skipping an entire major
version increment.
--Kris