Triaging

Differences between revisions 1 and 3 (spanning 2 versions)
⇤ ← Revision 1 as of 2008-03-27 15:10:42 →
Size: 569
Editor: ck523187-a
Comment: First version of this page
← Revision 3 as of 2008-03-27 23:58:47 → ⇥
Size: 895
Editor: wlan201
Comment: added new category, and added openswan
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
'''Back-end'''
 * ["Bugs/Triaging/HAL"]
 * ["Bugs/Triaging/LVM"]
 * ["Bugs/Triaging/Udev"]

'''Network/kernel'''
 * ["Bugs/Triaging/Openswan"]
Line 5: Line 13:
 * ["Bugs/Triaging/Firefox"]
Line 6: Line 15:
 * ["Bugs/Triaging/GNOME/Gconf"]
 * ["Bugs/Triaging/GNOME/NetworkManager"]
 * ["Bugs/Triaging/GNOME/PowerManager"]
 * ["Bugs/Triaging/KDE"]

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.

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)