Re: PEAR QA function definiton

Tobias Schlitt wrote:

Here a short summary of the functions QA should perform in PHP (in no special order). It's a very high level view on the functionality, since IMHO the concrete implementation should be done by the QA core group (as soon as defined) in cooperation with PEAR core group, to get faster results. - Check packages for: - Unmaintanedness

And know how to best reach the maintainers and their usual turn around time.

- Standard validation (Naming conventions, Group,...) - Check releases for: - Version validation - CS validation - Availability of peripherie (tests, docs, examples,...) for defined stadia ( - Functionality)

In the spirit of Jon's suggestion of preventing issues before they get released QA should also try to monitor cvs commits for issues. Furthermore QA can help developers improve their code by suggesting improvements. Run tests and generally help to build up infrastructure to automate testing as much as possible.

- Check bugs - Check for unmaintaned bugs - Bring developers and bug reporters in contact

regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07