Changes between Version 169 and Version 170 of ProjectInformation


Ignore:
Timestamp:
12/10/10 16:07:08 (11 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProjectInformation

    v169 v170  
    107107  * If the description of how to make the bug happen is clear, and the bug is gone...
    108108   * If there are also suggestions for improvements, and those haven't been done, add a reply that you've verified the bug is gone, and change the type to "enhancement".
    109    * Otherwise, add a reply to the ticket: Describe carefully what you did to test it, and "resolve" the ticket as "invalid". (The person who reported the bug can still reply and reopen the bug if they want.)
     109   * Otherwise, add a reply to the ticket: Describe carefully what you did to test it, and "resolve" the ticket as "worksforme". (The person who reported the bug can still reply and reopen the bug if they want.)
    110110  * If the instructions to cause the bug to happen aren't clear, try to figure out what the reporter meant -- try to find the bug yourself. If you can reproduce the bug, add better "how to reproduce" instructions.  See the [wiki:BugReportingGuidelines Bug Reporting Guidelines] for what makes a good bug report.
    111111  * If you can't figure out what the ticket means, add a reply that tells the ticket reporter what info would be helpful.