Re: An alternate view of PEAR QA

From: Date: Tue, 20 Jan 2004 03:39:16 +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-386@lists.php.net to get a copy of this message
On Mon, Jan 19, 2004 at 09:25:28PM +0100, Lukas Smith wrote: > Well no CVS means you dont have access to the history which makes > the job harder and relegates QA to a pure "nagging" job. First, the history of changes is available in the form of the release's <changelog> notes. Second, quality assurance is not a glamorous job. It is, however, both important and rewarding. I'm starting to get the feeling that my experience with software- related quality assurance groups differs from many of you here. Perhaps that explains the differing opinions. > It also makes it harder to handle orphaned packages, but thats > another story. Yes, orphaned packages have little bearing on the quality of released packages. Packages become orphaned after the fact. > >I'm not trying to be unrealistic, but I don't think there's another > >way to perform proper quality assurance. > > Well I fear you are. However I wish you are not :-) > I dont know if trying either system will hurt in the long run. Like > trying my proposal will make moving to the other system harder > (eventhough its the ideal) or if your system will turn into a fiasco > that will hurt PEAR and the general interest in PEAR QA. Maybe its also > not that big a drama either way. I don't think moving forward with either of those attitudes will be very productive. > >If we're really just talking about forming a group whose job is to be > >on alert for potential problems that occur in released packages, it's > >no longer a quality assurance group; instead, it's a live maintainance > >group. > > true .. QA sounds better though :-) Maybe we've been talking about two different things all along: I'm advocating a package-centric QA system that focuses on verifying the quality of individual releases. You're advocating a system that appears to focus on the overall quality of PEAR itself (which is why you've included plans for managing the package index and orphaned releases). We're approaching this from two opposing directions. At least that gives us a chance at meeting in the middle. =) Still, if we're not going to aggressively QA each package release, why do we need a QA team at all? It sounds all we're going to be doing is creating and empowering an entity that has the ability to fix broken package releases in the event of the package's maintainers not being available to fix problems themselves. -- Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)

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