Re: An alternate view of PEAR QA
| From: | Pierre-Alain Joye | Date: | Mon, 19 Jan 2004 21:06:02 +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-382@lists.php.net to get a copy of this message | ||
On Mon, 19 Jan 2004 21:25:28 +0100
Lukas Smith <smith@backendmedia.com> 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.
For what I understand CVS will be used read only, obviously. If we like
to get an history of the patches that have been used in a QA release
then we can easily store them on pearweb. Once the maintainers come back
it's easy to use the patch and update the CVS and/or their local dev
tree. We should not forget QA always sends the patches first, and only
if no commit withing the N days, release a"QA release".
> how many packages have test suites (and how much they actually cover
> of the API). finally we should consider how long QA'ing a release
> should take. maybe we need a survey that all devs need to fill out.
And how many people run them ;)
pierre