Work on the Bug Reporting System (00/08/06)

From: Date: Mon, 07 Aug 2000 00:15:04 +0000
Subject: Work on the Bug Reporting System (00/08/06)
Groups: php.qa 
Request: Send a blank email to php-qa+get-528@lists.php.net to get a copy of this message
Hrm... well, that was spastic.. here are the notes... Quick Overview Of Bug Report Process ------------------------------------ User enters the guided bug report interface. Guided Bug Report Interface --------------------------- Step 1: Gather / Validate User Information Step 2: Bug Overview Step 3: Gather Supporting Data This would include ini files, conf files, error and system logs, backtraces, etc... Step 4: Data Analysis / Display Similar Entries The system analyzes the entered data and searches for similar bug reports. These reports are then displayed. Step 5: Allow changes to bug status At this point, based on the information displayed in step 4, the user may set status flags to indicate that the bug is invalid, is already closed, is a duplicate, etc... Bug Hunter Bug Report Interface ------------------------------- Step 1: Validate the bug report The bug hunter needs to ensure that the bug is well-described, valid, unique, reproduceable, etc... If the bug is not valid, then set flags to indicate this, along with flags to indicate why the bug was invalid. Step 2: Analyze the bug Valid bugs need to be analyzed to discover their root cause. Bugs that cannot be analyzed shall be mercilessly thrashed by stas. :) Step 3: Assign the bug Find someone to repair the bug. Step 4: Bug Cleanup Ensure that the bug fix is a good and that is gets integrated into the source. Where appropriate, develop tests to help prevent the re-occurence of the bug, modify documentation, etc... Set flags that indicate what actions were taken to cleanup the bug. Zak

« previous php.qa (#528) next »