|parrotcode: Tips for Bug Wranglers|
|Contents | Documentation|
docs/dev/wranglers.pod - Tips for Bug Wranglers
This document attempts to outline a set of "best practices" for dealing with bugs in Parrot's RT system. It is targeted at Parrot developers and "Bug Wranglers" and is not intended as advice or instruction for end users. Bug filing procedures for end users are documented in docs/submissions.pod.
A developer with sufficient permissions to modify the tickets in Parrot's RT system. All Parrot developers are expect to pitch in and help keep the bug tracker in a healthy state. This means you!
The Parrot bug tracker is currently the same as the Perlbug system used for Perl5 Development. It is available via HTTP at http://rt.perl.org. The Parrot issues are in the queue parrot.
Where New refers to a pre-existing bug sitting in the Parrot queue with a status of
Assign the issue to the queue spam.
RT doesn't handle that case in a graceful manner. Set the relationship 'dependent on' to the duplicate issue. Add a comment to the bug along the lines of "Duplicate of Bug #123" and change the Tag field to "duplicate".
Ask for more input.
Is the subject line in the format
"[TODO] subsystem - issue?
[TODO] bugs should have their status changed to
open to prevent them from appearing in a listing of
Is the subject line in the format
"[PATCH] subsystem - issue?
Make sure that there is actually a patch attached to the bug...
This way you will receive further correspondence about the ticket.
If the bug is more then 1 month old then it's considered an old bug.
Give the requestor at least 1 week to respond.
If no response is received then add a comment to the bug saying that the bug is being close because of no response from the requestor change the status to
If it's a [PATCH] bug it's possible that the patch was applied but the bug/patch status was never changed. Also, not all list traffic regarding a bug ends up in RT. It's best to look at the SVN repo to attempt to determine if the bug was resolved.
Remember that every word you type into the bug tracker is On The Record. Try not to say anything that could offend or hurt the feelings of anyone. That includes the bug submitter and other developers. When, as a Parrot developer with commit rights, you send correspondence you are representing the Parrot project and by proxy TPF. If in doubt, either send the message privately or not at all.
Try to add a little token of appreciation to every message you send in response to a bug. Bug requestors are doing labor for free! The least you can do is let them know that you appreciate their efforts.
Thanks, Thanks for following up. Thanks for reporting. Thanks for X!
Can work wonders. If you can make someone feel good about themselves maybe they'll submit another bug/patch/whatever or perhaps some day become a Parrot developer.
Supposedly it's better customer relations to use issue(s) instead of the problem(s). Don't ask me why...
Always note why the bug is having it's status changed. Particularly if it is being closed or rejected. Nothing will irritate people more then letting them think that their bug was unimportant or ignored.
Hi, Can you retest for this bug with the latest sources from SVN and confirm that this still an open issue? Thanks, -J
Hi, Would you mind retesting with the latest sources from SVN? Thanks, -J
Hi, Can you resubmit this patch different against SVN trunk? Thanks, -J
Patch applied as rXXX. Thanks for submitting. -J
No response for requestor. Bug being marked as 'rejected'. Thanks for reporting. -J
This doesn't appear to be an issue anymore. Thanks for submitting -J
Marking this bug as 'resolved' because it seems to have fixed itself. Thanks for following up. -J
Joshua Hoblitt (JHOBLITT)