Re: Quality control of PECL modules

From: Date: Thu, 23 Feb 2006 02:34:26 +0000
Subject: Re: Quality control of PECL modules
References: 1 2 3  Groups: php.pecl.dev 
Request: Send a blank email to pecl-dev+get-3519@lists.php.net to get a copy of this message
On 2/23/06, Andi Gutmans <andi@zend.com> wrote: > Hey, > > I got lots of question about which PECL modules are stable and which aren't. > Any interest of coming up with some system where we give official > marks to these modules as to their stability? > We could come up with criteria which include: > a) Maturity > b) API stability > c) Test suite > d) Active maintainer > etc... > I haven't thought it through too much but I think we could create > some mechanism which would work. Having users vote would be another > valuable input but I don't think it'd be enough. We might want to > have 3 or four different ratings such as "very stable", "pretty > good", "not thoroughly tested", "crap/unfinished" :) > > Any thoughts? Yes, I have some :) As a first action, we should mark dead extension moved from php-src as dead, both in the manual and in the pecl.php.net site. I'm writing a full set of specs which are basically what I tried to propose when pecl began to be independent. Without going to the extremes used in PEAR (which are good but inappropriate in pecl), there is a real need of a minimum set of rules. One of them will be the quality/state. My actuall worry is about the intense usage of cvs snaps instead of stock releases (for example on windows). I will come with a RFC as soon as possible, next monday max. --Pierre

« previous php.pecl.dev (#3519) next »