Re: An alternate view of PEAR QA, so what?
| From: | Pierre-Alain Joye | Date: | Thu, 22 Jan 2004 16:09:54 +0000 |
| Subject: | Re: An alternate view of PEAR QA, so what? | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-397@lists.php.net to get a copy of this message | ||
On Thu, 22 Jan 2004 15:36:38 +0100
"Klaus Guenther" <klaus@capitalfocus.org> wrote:
> As an aside, it would be cool to have QA-approved releases going to
> the PFC directory, while normal releases of the packages would be
> handled in a simple way. Right now, we have a few packages that are
> bundled with PHP (see Lukas' forward on php-dev). That's where I could
> imagine it would be a very good thing to have QA give a stamp of
> approval before they are then released with PHP. This is something we
> will have to think about later, but I wanted to bring it up.
I like to bring that before any other thing.
FYI, I take care about the bundling stuffs and installer (go-pear).
Before every release I requested tests in the QA list (here :) ). See
the archives for the results...
This is the most important thing to do, be sure that PEAR itself (and
its frontends) works like a charm.
See Greg's posts about howto run the tests. About go-pear I like to have
feedbacks too, using any kind of operating systems.
As the amount of bundled packages are quit small (and will be even
smaller in a near future), that should be a perfect test cases for the
QA team.
I have to finish the current upgrade of go-pear (the last version, at
least using the current system). That means it will support other SAPI
than php as an apache module for the web frontends (IIS, CGI).
pierre