Derick Rethans wrote:
On Thu, 15 Sep 2005, Peter Brodersen wrote:
I guess my only real suggestion is that some of the template-answers
could be better worded.
Feel free to send a patch, and that was not meant as an attack.
I wrote this sometime back; it may be out of date.
Chris
---------
1. Change the way standard bug templates that are inserted. Currently
they appear above any additional developer comment. It is too easy
to miss the comment. A simple order change and <hr> break to
visually separate the custom text from the template text would fix
this.
2. Change some of the template text. Here are some potential changes.
(i)
"Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely to
be the same."
could be changed to
"An existing bug report [link to other bug here] already describes
this very problem. Please review it because the resolution is
almost certainly the same."
(ii)
"Please try using this CVS snapshot:"
could be changed to
"[Because X, or We think it might be fixed already, or Some other
nice text]. Please try using this CVS snapshot:"
(iii)
"Sorry, but your problem does not imply a bug in PHP itself. For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system is not the
appropriate forum for asking support questions. Due to the volume
of reports we can not explain in detail here why your report is not
a bug. The support channels will be able to provide an explanation
for you.
Thank you for your interest in PHP."
could be changed to
"Your problem does not seem to be a PHP bug. You can find more
help on using PHP at http://www.php.net/support.php. Search the
web and use the many PHP support forums to ask about your problem.
Thank you for your interest in PHP."
(iv) Do you have a "not enough info" message? Something like:
"You have not provided enough technical information to assess this
bug. Review other PHP bugs to see what kinds of problems are
considered bugs, and to see the quality of information required to
log a bug."
3. Ponder changing the "Bogus" status text to "Not a bug"
4. It's been a while since I logged & updated a bug. Is there a clear
message/reminder for bug loggers who add text telling them to
change the status from Bogus/Feedback/etc to Open?
5. Allow non-loggers to reopen bugs recently marked bogus.
--
Christopher Jones, Oracle Corporation, Australia.
Email: [EMAIL PROTECTED] Tel: +61 3 8616 3622
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
