Re: jump starting the qa team
| From: | Lukas Smith | Date: | Sun, 18 Jan 2004 21:39:44 +0000 |
| Subject: | Re: jump starting the qa team | ||
| References: | 1 2 3 4 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-366@lists.php.net to get a copy of this message | ||
Jon Parise wrote:
On Sun, Jan 18, 2004 at 10:29:53PM +0100, Lukas Smith wrote:yes. however pear qa will try to address issues in a more direct manner so to say than a developer might. obviously whatever qa does needs to pass the test suite etc. but qa's solution to a problem might not be what the developer wants to have in the package in the long term. since qa only fixes bugs and does not add features there shouldnt be a feature regression and obviously qa will try to make sure that whatever they fixed makes it into HEAD. however i think it would be really annoying if qa would just commit to head .. especially since head might have some feature enhancements. so they really need to branch from the last release tag. 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 07Yes, 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.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.