Re: [RFC] Versioning rules for PHP/Zend/PEAR/Extensions
| From: | Andrei Zmievski | Date: | Tue, 25 Sep 2001 13:38:16 +0000 |
| Subject: | Re: [RFC] Versioning rules for PHP/Zend/PEAR/Extensions | ||
| References: | 1 2 3 4 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-66545@lists.php.net to get a copy of this message | ||
On Tue, 25 Sep 2001, Stig Sæther Bakken wrote:
> I think we should be flexible to make this practical, the core of the
> idea is that you should not get any surprises when upgrading just "b",
> and no API surprises when upgrading "m".
>
> There's a question about whether the API should be defined as the
> source API, or also the runtime API, for extensions. I think "the
> API" should cover both.
But then you will quickly get into double digits for the 'm' version.
> > We already have such versions, they are called strnatcmp() and
> > natsort().
>
> Huh? Does strnatcmp() know the that 2.0RC4 is newer than 2.0b2? :-)
Well, geez, you had to go and spoil it with one example. :)
-Andrei
"Tomorrow the sun will rise. And who knows what the tide will bring?"
- Tom Hanks, in "Cast Away"