Re: An alternate view of PEAR QA

From: Date: Sun, 18 Jan 2004 23:20:34 +0000
Subject: Re: An alternate view of PEAR QA
References: 1 2 3 4  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-374@lists.php.net to get a copy of this message
On Mon, 19 Jan 2004 00:06:25 +0100 "Klaus Guenther" <klaus@capitalfocus.org> wrote: > If it is merely testing, that's not such a big deal. I thought you > were proposing that package maintainers can run things by QA for > input. If it is only for the purpose of testing, then I see your point > and would agree that that kind of release could be useful. However, it > should be available via the main pear server(install > Package-checkpoint) or whatever. But I'd still like to stress that QA > shouldn't take over pear-dev's functions. Let clarify a bit what means testings: - BC (can be partly automated soon, fully if php5 is used) - run unit tests These two points have never raised on peardev (or too late to act nicely). Note that they neither raised on pear-qa. > OK, I get your point. However, I do see some potential in requiring QA > to keep the PEAR core package (installer, etc.) unit tests up to date > (as needed). Greg has been doing a great job, but maybe we can help > out from time to time. Well keeping them update is not that an usefull task if we do not receive any test result, feedback or whatever, from pear-dev or pear-qa. Take an example, 1.3b5 is out, there are obviously pending "bugs", only Jan and a couple of devs reported something. That's not something to make me think about pear-dev interest in QA (except the classic things about naming convention ;) ). I like the concept of QA approved releases. Many things can be automatic. But many require feedbacks, from run-tests (wondering if we can get the pear related tests from php tests (make tests) ). pierre

« previous php.pear.qa (#374) next »