Re: List Idea

I think we should pick major platforms/configurations to be tested and assign members to certain configs. That way we can make sure we cover as much as possible and remain consistent. It might also be a good idea to have somebody try to stay up with the major bugs to make sure they get tested. I'm also thinking we might brainstorm and come up with some sort of standard checklist of issues and tests we run on each platform. We could have some sort of reporting system. Alot of vague ideas but I'm just trying to get the juices flowing. Any ideas? Comments? Jason ----- Original Message ----- From: "Zak Greant" <zak@nucleus.com> To: "Dave" <dave@cc0.net>; <php-qa@lists.php.net> Sent: Thursday, June 29, 2000 7:01 PM Subject: Re: [PHP-QA] List Idea > At 05:59 PM 6/29/00 -0700, Dave wrote: > >Will the QA participants be involved at all in closing bug reports or will > >they simply be testing PHP on different platform/environments? > > I would guess that the QA team will end up closing many of the spurious > reports where people are reporting syntax errors as bugs. > > >If the latter, would it be wise to have a closed list so QA members and > >Developers are the only ones who can post to the list? So as to avoid being > >bombarded with bug reports and general traffic? > > I believe that the existing mechanisms for reporting bugs would remain in > place. The list would mostly be a place for QA team members to discuss > issues with testing methods, etc.. > > > > Zak Greant > Creative Director > Nucleus Information Service Inc. > > "A camel is a horse designed by a committee." > - Alex Issigonis (Designer of the Mini) > > > -- > PHP Quality Assurance Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-qa-unsubscribe@lists.php.net > For additional commands, e-mail: php-qa-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net > > _______________________________________________________ Site Design, Hosting, and E-Commerce at www.webpipe.net