167
edits
QA/Triage: Difference between revisions
Jump to navigation
Jump to search
m
Added [checkin needed] status whiteboard tip
(→How to Deal with Ignored Bugs [Needs work]: first stab at "warning") |
m (Added [checkin needed] status whiteboard tip) |
||
| Line 144: | Line 144: | ||
# Bugs that have had review requested, but not from a specific person. This often happens by mistake of the reviewer name was entered incorrectly, in which case Bugzilla will flag the patch for review but not assign that to someone. These review requests are almost always ignored. If you think this is a mistake, try to assign to the review request to someone appropriate (this takes experience). If you're not sure, ping the patch author and ask them if it was intentional. | # Bugs that have had review requested, but not from a specific person. This often happens by mistake of the reviewer name was entered incorrectly, in which case Bugzilla will flag the patch for review but not assign that to someone. These review requests are almost always ignored. If you think this is a mistake, try to assign to the review request to someone appropriate (this takes experience). If you're not sure, ping the patch author and ask them if it was intentional. | ||
# Bugs where the patch author asked the reviewer a question, and received no answer | # Bugs where the patch author asked the reviewer a question, and received no answer | ||
# Patches which are reviewed but no one checked them in. Believe it or not, this happens all the time. Either the developer forgot, or did not have the correct CVS permissions to make a checkin. In this case they're supposed to request help from a developer with permission to check in. If they don't know that, a perfectly good fix may just sit there rotting away. | # Patches which are reviewed but no one checked them in. Believe it or not, this happens all the time. Either the developer forgot, or did not have the correct CVS permissions to make a checkin. In this case they're supposed to request help from a developer with permission to check in. If they don't know that, a perfectly good fix may just sit there rotting away. It's best to add "[checkin needed]" to the status whiteboard to let people know that the bug has a patch that needs checking in, or to remind the developer who made the patch to check it in. | ||
== How to Deal with Ignored Bugs [Needs work] == | == How to Deal with Ignored Bugs [Needs work] == | ||