Fw: [PHP-DEV] PHP/QA Update #2

From: Date: Fri, 28 Jul 2000 07:26:49 +0000
Subject: Fw: [PHP-DEV] PHP/QA Update #2
Groups: php.qa 
Request: Send a blank email to php-qa+get-364@lists.php.net to get a copy of this message
----- Original Message ----- From: "Cheng, Cheng-Wei" <cwcheng@mindspring.com> To: "Zak Greant" <zak@php.net>; <php-qa@lists.php.net> Cc: <php-dev@lists.php.net> Sent: Thursday, July 27, 2000 8:24 PM Subject: RE: [PHP-DEV] PHP/QA Update #2 > question/suggestion from me: > how will we go throught the steps and remove or update the deedback status > bugs This will depend on the situation... Here is what I will probably do... try to contact the user if this fails, look for duplicate bugs if a duplicate exists close the bug if no duplicate exists and the bug seems serious, try to reproduce the bug > can we try to identify assign developer by platform > then by problem? for compilation or platform specific issues, this makes the most sense - for other issues, we should probably do it by problem instead. > is there an interface on the php site for QA group to > update the status bug? Not unless they have a CVS account. > And can we be emailed with problem we sign up to. > may be like run a report from the web interface then emailed to us? The reports are mailed to the php-dev list. > May be the developer will not have the platform for them > self to test on. if the issue is too difficult to tackle then we can > try to escalate to other developer. Absolutely >And for module specific problem > we can always try to assign to module specific developer. Most likely. Zak

« previous php.qa (#364) next »