Re: Additional work on bug reporting system

From:	waldschrott	Date:	Fri, 04 Aug 2000 10:34:52 +0000
Subject:	Re: Additional work on bug reporting system
References:	1	Groups:	php.qa
Request:	Send a blank email to php-qa+get-462@lists.php.net to get a copy of this message

expert interface: it would be great to be able to add comma-separated-keywords(TM) to any bug-report, would allow to assign all ISAPI and other important bugs "4.0.2" to let people it should be fixed before releasing 4.0.2, or yould add "help", whatever Zak Greant wrote:

Hello all, I have added a bit more to the reporting system - see below for new work - note changes made to existing work Zak Welcome to the PHP Bug Reporting utility. The utility comes in two different flavors. [x] Guided Bug Submission
    - helps solve problems that are already known and fixed
    - easy to use
    - excellent for both experienced and inexperienced users
[ ] Expert Interface
    - intended for expert level users
    - faster to use
    - more detailed
============================================================ Guided Bug Submission ============================================================ Step 1: User Information ------------------------ Please tell us a little bit about yourself. Being able to contact you when we are investigating a bug is very important. Bugs often occur due to a combination of factors that do not or have not occurred in our testing process. You may be the only person who can reproduce the bug or confirm that it has been fixed.
Your Name (or Handle) [           ]
Email Address [           ]
Confirm Email Address [           ]
Password [           ]
Confirm Password* [           ]
* Only if creating a new account. If you have not submitted a bug report before, then a new account will be created for you. This account will allow you to modify the bug reports that you submit. Confirmation of your account creation, along with your chosen password and name will be emailed to you. Once you have submitted a bug, a report on the bug's status will be emailed to you until the bug is closed or you disable the email notification for the bug. Reports are send out every two weeks and each time that the bug changes status. Step 2: Bug Overview -------------------- The bug overview step allows us to gather basic information about the bug. This information is used to: * Search for problems that are similar to yours * Offer possible solutions to your problem * Determine what questions to ask you about the bug Were you able to compile PHP? [ ] Yes [ ] No [ ] I used a binary from the PHP site. [ ] I used a binary from another source.
    Please enter the source name (and url, if applicable)
    [              ]
Were you able to install PHP? [ ] Yes [ ] No [ ] PHP was installed by someone else [ ] PHP was preinstalled on the system Can you run PHP scripts? [ ] Yes [ ] No What version and type of PHP are you using?
[ Version ] [ Type *         ]
            [ Apache Module  ]
            [ ISAPI          ]
            [ NSAPI          ]
            [ CGI Executable ]
            [ etc...         ]
* I am not sure what to call this... What operating system are you using?
[ Operating Systems ] Other: [     ]
What web server are you using?
[ Web Servers ] Other: [     ]
Can you recreate the bug? [ ] Always [ ] Sporadically [ ] Never What features or functions are affected?
[                                      ]
Please enter any error messages generated by the bug.
[                                                   ]
Step 3: Analyze Data -------------------- Except for processing time, this step is transparent to the user. The utility compares existing entries in the bug database for similarity. It tries to find related entries by matching up pieces of data in the individual fields. Step 4: Display Similar Entries ------------------------------- If the utility finds any likely matches to the bug report, it will generate a list of what it has found. The list is sorted by the strength of the match, and then by the bug status - sorting from Closed to Not Reviewed. A quick synopsis of each entry, along with a button that allows the current bug to be flagged as a duplicate of an existing bug, will be displayed. If the user chooses to flag the current bug as a duplicate of an existing bug, then several things can happen. If the existing bug is closed, then the entry of the bug report will be ended. In any other case, the bug reporting process will continue. Optional Steps ============== If the user was unable to compile PHP ------------------------------------- Please describe the steps that you followed to attempt compilation.
[                                                   ]
[                                                   ]
[                                                   ]
[                                                   ]
[                                                   ]
If the user was able to install PHP ----------------------------------- Please enter your php.ini file
[                                                   ]
[                                                   ]
[                                                   ]
Please enter your server configuration file
[                                                   ]
[                                                   ]
[                                                   ]
Please enter your php.ini file
[                                                   ]
[                                                   ]
[                                                   ]