From Fedora Project Wiki
m (→Triage Check List: typo) |
(integrate BugZappers/Special Procedures) |
||
| Line 8: | Line 8: | ||
#* changing them to ASSIGNED if [[BugZappers/BugStatusWorkFlow#ASSIGNED | sufficient information]] is present to reproduce or fix the bug | #* changing them to ASSIGNED if [[BugZappers/BugStatusWorkFlow#ASSIGNED | sufficient information]] is present to reproduce or fix the bug | ||
#* set the ''NEEDINFO'' flag if insufficient information is present | #* set the ''NEEDINFO'' flag if insufficient information is present | ||
#* | #* Please do not triage bugs filed against the "Package Review" component, which usually have "Merge review" in the summary. These are handled as part of the [[Package Review Process]]. | ||
#* Requests for new packages to be added to Fedora should be closed NOTABUG and added to the [[Package maintainers wishlist]]. See the [https://fedoraproject.org/wiki/BugZappers/StockBugzillaResponses#DRAFT:_Request_for_a_package_to_be_added_to_Fedora stock response]. | |||
#* See [[BugsAndFeatureRequests]] for more advice on particular components | #* See [[BugsAndFeatureRequests]] for more advice on particular components | ||
# Reviewing bugs with ''NEEDINFO:reporter'' flag set for more than thirty (30) days | # Reviewing bugs with ''NEEDINFO:reporter'' flag set for more than thirty (30) days | ||
Revision as of 15:13, 11 March 2009
See BugZappers/FindingBugs if you need to get a list of bugs to work on.
Triage Check List
Here is a check list of regular things to check for:
- Reviewing bugs in a states of NEW
- changing them to ASSIGNED if sufficient information is present to reproduce or fix the bug
- set the NEEDINFO flag if insufficient information is present
- Please do not triage bugs filed against the "Package Review" component, which usually have "Merge review" in the summary. These are handled as part of the Package Review Process.
- Requests for new packages to be added to Fedora should be closed NOTABUG and added to the Package maintainers wishlist. See the stock response.
- See BugsAndFeatureRequests for more advice on particular components
- Reviewing bugs with NEEDINFO:reporter flag set for more than thirty (30) days
- At this point send a reminder and then if there is no response after another thirty (30) days close it.
- Is the bug a duplicate?
- This is the most common type
- Is this bug a duplicate of a previous solved or unsolved bug?
- See Finding Duplicates for more information on the master art of finding duplicates
- Does the bug need more information from the original reporter?
- Is enough information present about the reporter's system?
- Are clear instructions present about how to reproduce the bug?
- Has the reporter included sufficient troubleshooting information or error logs?
- Are there attached screenshots for GUI bugs?
- Is the reported bug related to another bug that has already been reported?
- Would solving one bug help the other?
- Is the bug reported under the correct bugzilla component (source package)?
- See determining the correct component
- For example, if someone reported a problem running Firefox in GNOME, should the bug be filed under Firefox or GNOME?
- Is the bug reporting more than one problem--a Two-in-one bug.
- Should this bug be split into two bugs?
- If you aren't sure get a second opinion from another triager or developer on IRC.
- Is the bug already fixed?
- If someone has confirmed it is fixed add a comment to that affect and close it.
- If a fix has not been confirmed suggest trying the latest build from Koji Build System
Going Deeper
- Bugs to triage: Finding Bugs
- Understanding the differences between Bugs and Features .
- Bug state flow: Bug Lifecycle
- Hints for doing:
- Understanding things that Bugzilla does automatically
General Advice
- Please remember to be polite when triaging bugs; we would like reporters to continue doing so in the future.