Re: getting a QA'ed package release
| From: | Pierre-Alain Joye | Date: | Thu, 04 Mar 2004 21:20:33 +0000 |
| Subject: | Re: getting a QA'ed package release | ||
| References: | 1 2 3 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-827@lists.php.net to get a copy of this message | ||
On Thu, 4 Mar 2004 22:13:30 +0100
klaus@capitalfocus.org (Klaus Guenther) wrote:
> The problem is that it adds unnecessary overhead while the
> advantages are rather low. We don't want a situation where a
> package sits there for a week while the QA team is processing
> other packages. This idea has been brought up before. While it is
> necessary in a corporate setting, it doesn't quite work for PEAR
> yet.
What is worst? Wait a few days (in worst case) for a release or bork
user installation?
Experenciences show me that even an asynchronuous approval is a bad
thing. Noone acts fast enough. For instance who saw that
Net_UserAgent_Detect was a bad release? Either yesterday evening and
today?
About PFC, or similar principles, I'm strongly in favour of a
approval before the official release. No, I will oppose anything
else for any package required by the installer or the packages
manager. As soon as possible I will try to reduce them to a minimum
and bundled only those required.
pierre