Re: An alternate view of PEAR QA

From: Date: Mon, 19 Jan 2004 09:03:38 +0000
Subject: Re: An alternate view of PEAR QA
References: 1  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-377@lists.php.net to get a copy of this message
Jon Parise wrote:
Here are my musings on the role of the PEAR QA team:
To that end, the QA team's job starts just after a package release is submitted by a developer. The release is marked as "pending approval by QA" and won't become a public release until the QA team blesses it. The QA team has the ability to fail the release, essentially sending it back to the developers for improvement.
This proposed system aims to prevent "bad" packages from ever being released into the wild. Unfortunately, mistakes do happen, and we'll probably have to adopt most of Lukas' proposals [1] to deal with those kinds of situations when they occur.
The reason why I proposed a different system was not because your proposal is not what we ideally want, but that its simply unrealistic with the means we have today. We dont have enough people that will dedicate their time to PEAR QA. Furthermore packages dont have test suites (and we havent made that a requirement either). Packages dont even have to reside in any CVS atm. Thats why I dont see that we can really monitor the changes, test the changes and provide feedback within a reasonable timeframe. The system I proposed is more geared to be realistic solution and not so much the ideal. However we shouldnt give up that ideal and maybe one by one we will be able to increase our standards to also require test suites, everything in (atleast synced into) PEAR CVS and tons of willing and able people that will make sure that this QA process doesnt turn into a hassle but more into a great source of people making sure that your package works as intended. regards, Lukas

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