Re: jump starting the qa team
| From: | Jon Parise | Date: | Sun, 18 Jan 2004 21:36:29 +0000 |
| Subject: | Re: jump starting the qa team | ||
| References: | 1 2 3 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-365@lists.php.net to get a copy of this message | ||
On Sun, Jan 18, 2004 at 10:29:53PM +0100, Lukas Smith wrote:
> >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.
Yes, that was clear.
I'm suggesting that the package developer will probably need to merge
any QA-committed changes from a QA branch into the package's mainline
development tree before a new package release is made. Otherwise, end
users will see a regression.
I'm assuming that a QA release is, for all intents and purposes,
simply another package release like any other, albeit with some kind
of addition "this is a QA release" decoration.
--
Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)