Re: jump starting the qa team

From: Date: Sun, 18 Jan 2004 23:19:57 +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-373@lists.php.net to get a copy of this message
Jon Parise <jon@php.net> wrote: > 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 think it should be specifically marked as a QA release. For example, consider: HTML_Page2 2.0 stable HTML_Page2 2.0.1 qa The qa release should be treated as having the same stability as the numerically preceding release. In the above example, the qa release would have the status stable. The QA team should immediately inform the maintainer of the package and provide a patch with additional documentation. In most cases, though, it will probably be easier (and better) to simply revert the release if it creates huge problems. Jon's alternative proposal prevents such releases from being necessary in most cases -- but still does not address problems such as missing files if the unit tests aren't complete. In such cases, it would be the right thing to allow for qa releases. I think a merger of Lukas proposal with Jon's proposal (which would only apply to stable releases) would provide an optimal solution. Klaus

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