Newsgroups: php.internals,php.pecl.dev
Path: news.php.net
Xref: news.php.net php.internals:25708 php.pecl.dev:4130
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.182.184 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=j2ml4YNdvdQ2TtjYW6vvq9BauVjPZMzE9aYczGKUBONLSSTxGSC3KfBxUUX2vEs5KoPswpLaS649lNx60DrLUXi6KjE2yplfAshAUPRJ9RLR7IlX9gtFplISEvpHY5QMaj8ScuFMR0f3kMqGCRUi7sc7eNZB53Zu2mlr3QhSEB4=
Message-ID: <fe05d1540609141210r5666dd9dya3582bc94c5f62d8@mail.gmail.com>
Date: Thu, 14 Sep 2006 21:10:28 +0200
To: "Derick Rethans" <derick@php.net>
Cc: PECL <pecl-dev@lists.php.net>, 
	"PHP Developers Mailing List" <internals@lists.php.net>, 
	rasmus@php.net, "Ilia Alshanetsky" <ilia@prohost.org>
In-Reply-To: <Pine.LNX.4.62.0609141504130.3506@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <fe05d1540609141147w2bfc707djdd27134a0f66a245@mail.gmail.com>
	 <Pine.LNX.4.62.0609141504130.3506@localhost>
Subject: Re: [PHP-DEV] filter 0.10.1 release
From: pierre.php@gmail.com (Pierre)

Hello,

On 9/14/06, Derick Rethans <derick@php.net> wrote:
> On Thu, 14 Sep 2006, Pierre wrote:
>
> > 5.2.0RC2 has been released a couple of mins ago, just like the RC3
> > release,  I like to release a
> > bug fixes only Filter release. The three fixed bugs are:
> >
> > - filter.default has been fixed, it was broken in 0.10.0 and RC3
> > - Float filter handling of 02.324
> > - better fix of the test 035
> >
> > If there is no objection, I will release it tomorrow evening.
>
> Just hold that off for a bit because of the API changes.

I disagree, I really like to have this release to validate the fixes
and the implementation. It is really important to have the wider
possible audience. Having a PECL release that matches a PHP release is
fine, or what is good for a PHP release is not good for a PECL
release?

> > Derick, you told us on IRC that you like to have an API shake up, or
> > bring "consistency", I think it is now too late, we will not have any
> > other RC.
> >
> > If you convinced Ilia about a RC5, then I'm fine. If not it is, in my
> > oppinion, too dangerous to change that now. What's about post 5.2.0
> > while bringing the PECL filter package to 1.0.0-stable (a long road)?
>
> No, we need to have a consistent API. Final RC or not. I will not agree
> to introduce an new extension with a "broken" API.

You had months to disagree. I like consistency, I like stability even
more. I'm not saying that filter is stable, but its code will be
executed in every single install and will certainly be widely adopted,
we cannot take the risk to have a broken ext in 5.2.0. Short version:
wait or convince Ilia :-)

--Pierre