Re: An alternate view of PEAR QA

From: Date: Mon, 19 Jan 2004 21:01:47 +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-381@lists.php.net to get a copy of this message
Lukas Smith wrote:
Jon Parise 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. It also makes it harder to handle orphaned packages, but thats another story.
Where is the problem with that? No QA member needs access to CVS. CVS is a tool for development and releases are a place for QA. If a release is broken, the QA can simply roll it back.
For reference, here are the goals (http://qa.php.net/projects.php) of the PHP QA team:
    - Release Candidate Build
    - Automated Smoke Tests
    - Automated QA Checklists
    - Automated Regression Tests
Well php has a lot of differences.
#1 they are much more closed in terms of adding new functionality #2 they are more open in regards to other people touching other peoples code #3 they have fairly long release cycles
#3a) they have a unique release date
#4 they are totaly undermanned #5 their tests hardly cover all the parts of php
Regards, Toby

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