On Mon, Apr 7, 2014 at 5:03 PM, Rowan Collins <rowan.collins@gmail.com>wrote:
> On 04/04/2014 02:16, Good Guy wrote:
>
>> The only time we should jump one number is when #13 is reached.
>>
>
> I guess we should avoid a 6th patch to the 6th minor version of version 6
> as well?
>
> Oh, and if you're going for the superstition angle, we've already messed
> up by not skipping version 4: https://en.wikipedia.org/wiki/Tetraphobia
>
> (Please tell me you were joking/trolling?)
>
> --
> Rowan Collins
> [IMSoP]
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Wow, I didn't know that the number 4 has its very own phobia. This is why
people should subscribe to Internals! You learn something new every day.
With regard to versioning, I propose that we devise a complex algorithm to
determine future feature numbers. The algorithm should follow at least the
following rules:
1. No prime numbers, UNLESS they're part of the Fibonacci sequence.
2. The number "6" should be replaced with a smiley face, ":)", to avoid
invoking a satanic curse.
3. Multiply the version number by -1 times the number of bugs fixed in that
version.
4. Every version must be followed by ", Presented by Burger King." If we
do it enough times, they'll have to pay us eventually, then we won't have
to look for a corporate sponsor.
5. Minor version increments are 11-indexed and must be expressed in
hexadecimal.
6. Maintenance version increments are 5-indexed must be expressed in binary.
Now that that's settled, let's focus our attention on feature planning for
the upcoming PHP -:).C.101, Presented by Burger King.
--Kris