Re: jump starting the qa team

From: Date: Sun, 18 Jan 2004 21:29:53 +0000
Subject: Re: jump starting the qa team
References: 1 2  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-364@lists.php.net to get a copy of this message
Jon Parise wrote:
On Sun, Jan 18, 2004 at 06:05:07PM +0100, Lukas Smith wrote:
2. PEAR QA has full control (this includes removing the package from the main index(*) all together and also includes adding notes to the package homepage) over how packages are listed in PEAR web and my make QA releases (by creating a CVS branch) or pull releases made by the maintainer
I'm the least comfortable with these abilities being granted to the PEAR QA team. I understand that the QA team needs to be empowered to act upon package problems, but I see potential for additional confusion to arise between developers and QA members, especially if QA members can creating QA branches where new code is committed to a package by QA people which becomes part of a QA release. The package's developers would become somewhat responsible for maintaining this QA-committed code, which is awkward.
uhm the idea behind the branch is that the developer will not become responsible at all for that code. the name of the branch should communicate that this is a qa branch. regards, Lukas -- 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

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