RE: [PHP-QA] Is a new bug reporting system needed?

From: Date: Fri, 30 Jun 2000 19:37:44 +0000
Subject: RE: [PHP-QA] Is a new bug reporting system needed?
References: 1  Groups: php.qa 
Request: Send a blank email to php-qa+get-55@lists.php.net to get a copy of this message
> There are mixed opinions on whether or not we need to rework the > bug database. > > Perhaps before the issue is decided we should consider the > following questions. > > What are the benefits of changing? > What are the drawbacks of changing? > Could we use an existing bug tracking system? > What is the best solution? > > ---------------------------------------------- > My personal opinions are as follows: > ---------------------------------------------- > > Q) What are the benefits of changing? > A) The new system could help smooth out the debugging process. > > Example of how this could be accomplished follow: > > Screening - If the system is constructed so that the user > needs to specify > the details of the bug before they enter details on the bug, then there > should be less duplication of bug reports. The system could be > designed to > help reduce multiple submits on the same bug. > > Confirmation - Bug reports could be assigned via an > automated distribution > system to active QA team members. They would then try to confirm the > bug. Many spurious errors will be caught this way. Bugs that > survive this > testing stage will be validated and brought to the attention of > the developers. > > Re-evaluation - Reworking the system would give us a change > to re-examine > bugs as they are encountered. This alone will close many bugs. > > Integration - Reworking the bug tracking system will allow > us to easily > incorporate features that will help the QA effort. It seems to me from what I've read the the real problem is a lack of people willing to work on squashing and verifying bugs. I'm not so sure that the system needs to be completly changed. I like a previous idea of modifying the system to allow us to view bug reports and possibly close duplicates and bogus reports. It might be a good idea to help screen them as well. If someone submits a really vague report, then we could help gather info so the developers don't have to do it. I think changing the system would be pretty time consuming and it doesn't seem to work all that bad. Jason _______________________________________________________ Site Design, Hosting, and E-Commerce at www.webpipe.net

« previous php.qa (#55) next »