Newsgroups: php.internals,php.pecl.dev
Path: news.php.net
Xref: news.php.net php.internals:36379 php.pecl.dev:5251
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.200.172 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=bJ7shxzXynEG2G40xz3PlHAHODgct/XnyrAHSilvQ2AYgCkrWdNO0IjlT97yH60Rx73STPF+hbdBf0b7iV08hdSjLvPz9SoPsdeZfwowijV5yOjcs8ezkQFfSCDoRu/58souVtP/FLbHziZDuwVLSqOWY2v6876IWqPXngMJatA=
Message-ID: <7f3ed2c30803230707g66b3aad4r99fd70d977078cce@mail.gmail.com>
Date: Sun, 23 Mar 2008 15:07:38 +0100
To: "Steph Fox" <steph@zend.com>
Cc: "=?ISO-8859-1?Q?Johannes_Schl=FCter?=" <johannes@php.net>, 
	internals <internals@lists.php.net>, pecl-dev@lists.php.net
In-Reply-To: <006d01c88cea$a4319d50$c6fc1f3e@foxbox>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <00dc01c88c90$c34c5cc0$c6fc1f3e@foxbox>
	 <7f3ed2c30803230501wc48cb3frda25564f59b32d06@mail.gmail.com>
	 <1206275969.31721.31.camel@goldfinger>
	 <006d01c88cea$a4319d50$c6fc1f3e@foxbox>
Subject: Re: [PECL-DEV] About that PECL versioning thing
From: hannes.magnusson@gmail.com ("Hannes Magnusson")

On Sun, Mar 23, 2008 at 2:34 PM, Steph Fox <steph@zend.com> wrote:
> Hi,
>
>
>  >> The first step in fixing the core<->pecl relationship? \o/
>
>  That's the basic idea, yes.
>
>
>  >> But what about extensions that are symlinked to core? Will they need
>  >> to update their version info during core release cycles?
>  >> It obviously shouldn't have a -dev version when distributed with PHP..
>  >> Is it up to the RM to hunt those extensions down and make sure the
>  >> version info is accurate?
>  >
>  > Just removing the "-dev" in the version number would be wrong (as is
>  > symlinking), a Stable PHP release should include "stable" extensions.
>  > Not dev versions of the extension. So one of the ideas is to fetch the
>  > last stable extension release for a PHP release, but well, then there's
>  > the problem that everybody (people using snaps, people using CVS, ...)
>  > end up with different versions which makes QA hard. (not to mention bug
>  > hunting trouble with people using the latest release but updated a
>  > single extension, ....)
>
>  But we already have those problems now. Labelling the version just makes it
>  more obvious that we have those problems :)

Exactly. So lets deal with one problem at a time Johannes.
But Steph: Your RFC doesn't mention how to deal with the problem.
During development the extension should be -dev... so who is
responsible to change it back during PHP releases?

-Hannes