Re: Bug System Rough

From: Date: Thu, 03 Aug 2000 16:11:32 +0000
Subject: Re: Bug System Rough
Groups: php.qa 
Request: Send a blank email to php-qa+get-414@lists.php.net to get a copy of this message
At 12:40 PM 8/3/00 +0200, you wrote:
Your Name (or Handle)   [                       ]
Email Address   [                       ]
Confirm Email Address   [                       ]
Password   [                       ]
Confirm Password (Only if creating a new account.) ]
rembember to include an easily accessible password reminder
Should we also send out their password when we remind them to update their bugs? Say bi-monthly or monthly.
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. 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 install PHP? [ ] Yes [ ] No
add; [ ] did not install, for PHP-space-provider users
True :)
Can you run PHP scripts? [ ] Yes [ ] No What version of PHP are you using? [ Version ]
note: the option "current CVS 4.0.0 (2000-08-02)" should be changed to regard the real version number "Latest CVS 4.0.2-dev (2000-08-02)"
Ok
What operating system are you using?
[ Operating Systems ] Other: [     ]
What web server are you using?
[ Web Servers ] Other: [     ]
Add: Module? [ISAPI,NSAPI,CGI...]
Sure
Can you recreate the bug [ ] Yes [ ] Maybe [ ] No
Subst: Maybe, what should it tell?
I do not understand - please elaborate
How much of PHP does the bug affect? [ ] All of PHP [ ] Multiple features or functions [ ] A single feature or function How important is the bug? [ ] Critical [ ] Important [ ] Trivial
These enhancements were meant dev-only, but we can change them afterwards surely, because the user isn´t serveral times in the position to decided this, keep it anyway this way. You´ve obscured my SCOPE proposal, it was meant for helping devs only to calculate the time needed to fix the bug, add this:
I have not included Scope in the Guided bug reporting system - how the heck do most people evaluate this. If they are able to do this, then they should be using the advanced editor.
Scope of fixing: - Large, serious rewrites/changes/thinking needed - Medium, imporant changes on one or more components needed - Small, trivial fix good work
Our good work! Zak

« previous php.qa (#414) next »