Re: PHP's vision
| From: | derick@php.net | Date: | Mon, 03 Jun 2002 09:43:06 +0000 |
| Subject: | Re: PHP's vision | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-84753@lists.php.net to get a copy of this message | ||
On Mon, 3 Jun 2002, Melvyn Sopacua wrote:
> At 10:18 3-6-2002, Markus Fischer shared with all of us:
>
> > This is true, but ... there is absolutely _nothing_ we can do
> > about it. The QA Team is, well .. sometimes I get the
> > impression it's only one person!
>
> Derick had a good thing going, when he emailed people who reported
> problems and needed confirmation of a fix. That stopped.
yes, unfortunately that stopped, because I don't have time to manage it
that tight. It costs a lot of time and doesn't gain that much at all. The
only reason I did this was to get the release as bugfree as possible. And
I only wrote people back who had problems with release candidates.
> Besides that - there's no involvement of QA when extensions get moved,
> broken or added new functionality - just at RC time.
That's how it is now, but in an ideal situation the tests should be
automated to run once a day so incompatabilities are found early.
> Yes - most of us, will read php-dev, but a heads-up when something major
> has changed with an extension is not a bad thing.
>
> This will allow the extension maintainer to fix things when it's still
> fresh - not when there's a release x weeks/months down the road, and he's
> devoted his time elsewhere and can't do anything about it anymore.
>
> > Until we prison some people
> > to do it, I think our QA or Release Management will not
> > improve that much. Other hot topics in this area would be
> > automated test system (more then the current make test does).
>
> The current (=4.3.0-dev) make test at least provides a consistent output
> and logging.
> With a simple command all reports can be collected:
> find . -type f \( -name "*.log" -a \! -name "config.log" \) -print | xargs
> tar -cpvzf ./failed.tgz
>
> Add that to the test target in the makefile and instructions on where to upload
> it, and you'll make test-reporting a whole lot easier.
that would help indeed..
Derick
---------------------------------------------------------------------------
Did I help you? http://www.jdimedia.nl/derick/link.php?url=giftlist
Frequent ranting: http://www.jdimedia.nl/derick/
---------------------------------------------------------------------------
PHP: Scripting the Web - derick@php.net
All your branches are belong to me!
SRM: Script Running Machine - www.vl-srm.net
---------------------------------------------------------------------------