Re: An alternate view of PEAR QA

From: Date: Sun, 18 Jan 2004 23:06:25 +0000
Subject: Re: An alternate view of PEAR QA
References: 1 2 3  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-371@lists.php.net to get a copy of this message
Jon Parise <jon@php.net> wrote: > > > Developers will be able to mark special "checkpoint" releases that are > > > sent directly to the QA team for testing and feedback. These releases > > > will never become public. > > > > I don't like this. QA shouldn't take over the function of the pear-dev list. > > I suppose I never considered testing one of the functions of the > pear-dev list. Up to this point, mosts of the QA-oriented functions > have been happening there, but it's my hope that this (pear-qa) list > will assume more of that role so that pear-dev can focus on package > development (and make the posting volume more manageable). 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. > Fair enough, although I don't think I was clear. I wasn't expecting > the QA team to write tests. I was merely suggesting that they should > have the ability to improve existing tests or submit news tests back > to the developments. I wouldn't consider authoring tests scripts as a > function of our QA group (although it is a core function of many QA > groups). 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. > If we were to follow the letter of the law, no > package would be released without tests and documentation. Which is precisely why I haven't released HTML_Page yet. > That's a good point. I only intended my proposal to apply to stable > packages. The complement is that a package couldn't become "stable" > until it passes through the QA process. Sounds reasonable to me. Klaus

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