Triaging

Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2008-03-27 23:58:47 →
Size: 895
Editor: wlan201
Comment: added new category, and added openswan
← Revision 4 as of 2008-03-28 15:47:09 → ⇥
Size: 1140
Editor: ck523187-a
Comment: Added things that need to be included at all times to a bug report
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:

Make sure this information is present in the bug report in all cases:
 * Release(s) of Ubuntu affected by the bug
 * Architecture(s) affected by the bug
 * Version(s) of the package(s) affected by the bug
 * Is it reproducible every time

Triaging is one of the most important parts of being a Bug Triager. This means that the bug report contains enough information for the developer to decide what's the problem. Especially when forwarding upstream it's important to have enough information so the developers upstream can look for the cause, especially since communicating goes a bit trickier with two bug tracking systems. This page contains an overview of information of what developers would like you to include with the bug report.

Make sure this information is present in the bug report in all cases:

  • Release(s) of Ubuntu affected by the bug
  • Architecture(s) affected by the bug
  • Version(s) of the package(s) affected by the bug
  • Is it reproducible every time

Back-end

  • ["Bugs/Triaging/HAL"]
  • ["Bugs/Triaging/LVM"]
  • ["Bugs/Triaging/Udev"]

Network/kernel

  • ["Bugs/Triaging/Openswan"]

Desktop

  • ["Bugs/Triaging/Firefox"]
  • ["Bugs/Triaging/GNOME"]
  • ["Bugs/Triaging/GNOME/Gconf"]
  • ["Bugs/Triaging/GNOME/NetworkManager"]
  • ["Bugs/Triaging/GNOME/PowerManager"]
  • ["Bugs/Triaging/KDE"]

CategoryBugSquad

Bugs/Triaging (last edited 2008-08-06 16:32:43 by localhost)