Re: getting a QA'ed package release
| From: | Klaus Guenther | Date: | Thu, 04 Mar 2004 21:13:30 +0000 |
| Subject: | Re: getting a QA'ed package release | ||
| References: | 1 2 | Groups: | php.pear.dev php.pear.qa |
| Request: | Send a blank email to pear-dev+get-26101@lists.php.net to get a copy of this message | ||
From: "Marshall Roch" <pear-dev@exclupen.com>
> Lukas Smith wrote:
> > However I would like to encourage people to mail Pear QA if they are
> > about to release a package so that we can have a quick look. Alot of the
> > recent issues (like stable release below 1.0.0, not handling a BC break
> > correctly) can be easily spotted.
>
> What about adding this to the release workflow, so that the new package
> doesn't get released until checked by QA?
The problem is that it adds unnecessary overhead while the advantages are
rather low. We don't want a situation where a package sits there for a week
while the QA team is processing other packages. This idea has been brought
up before. While it is necessary in a corporate setting, it doesn't quite
work for PEAR yet.
The asynchronous QA-seal of approval suggested by Sérgio would be a good
idea -- we already have talked about PFCs, which would require that.
Klaus