Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33086
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain daylessday.org designates 89.208.40.236 as permitted sender)
Message-ID: <47361AAB.90704@daylessday.org>
Date: Sat, 10 Nov 2007 23:55:07 +0300
User-Agent: Thunderbird 2.0.0.6 (X11/20070801)
MIME-Version: 1.0
To: Gaetano Giunta <gg@ez.no>
CC:  internals@lists.php.net
References: <47360449.3020007@ez.no> <47360BE3.7010207@daylessday.org> <4736156F.1040202@ez.no>
In-Reply-To: <4736156F.1040202@ez.no>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: PHP 5.2.5 Released - update on extensions versioning
 information
From: tony@daylessday.org (Antony Dovgal)

On 10.11.2007 23:32, Gaetano Giunta wrote:
> Checking dates, pecl 1.2.4 was released the day after php 5.2.4.

As I've already said, OCI8 and PHP releases are not synced.

> I do not need to scan this list's archives to be sure that everybody involved 
> in the oci code knew quite well about the pending release of php, and 
> changing that single line of oci code where the version is stored would 
> not have been a huge deal. If there really was no certainty that the php 
> code would end up being the same as pecl 1.2.4, it could have been 
> tagged 1.2.4-dev or something like that...

I don't understand what you're trying to say.
Do you mean that all PECL maintainers should update their extensions before PHP release?
 
> plus a 3 numbered version is very easy to assign to a lib (you know, 
> like a new param for a function bumps up the middle number, a fix - any 
> fix - bumps up the rightmost one etc... ) 

That is what $Revision$ CVS tag does, version number is totally different thing IMO.

-- 
Wbr, 
Antony Dovgal