Re: Quality control of PECL modules

From: Date: Thu, 23 Feb 2006 02:58:30 +0000
Subject: Re: Quality control of PECL modules
References: 1 2 3 4  Groups: php.pecl.dev 
Request: Send a blank email to pecl-dev+get-3522@lists.php.net to get a copy of this message
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). <response - don't know why your mail doesn't work like everyone else's mail> Pierre, before you even start throwing out RFCs you need to work with people that create win32 builds, and this is something that's either been lacking or non-public to date (not just from you). As I said to you on irc - and Edin agreed in theory, and I agreed to help implement - 'stock releases' should mean we have a PECL_STABLE tag on PECL releases regarded by their maintainers as stable. Those tagged versions - and no others - should go into the PECL bundle on the php.net downloads page with PHP releases. I don't see any reason to do anything further for win32 releases, and the rest are already covered. We _need_ to have the facilities that pecl4win already provide, both from the dev and the user perspective; there is no other way to reliably pick up fixes. What was the problem again? - Steph </response>

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