[Ubuntu Wiki] Update of "DebuggingGwibber" by kamus
Ubuntu Wiki
noreply at ubuntu.com
Mon Nov 8 20:14:34 GMT 2010
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The following page has been changed by kamus:
http://wiki.ubuntu.com/DebuggingGwibber
New page:
<<Include(Debugging/Header)>>
||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url('https://librarian.launchpad.net/1812570/bugsquad.png'); background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;">'''Contents'''<<BR>><<TableOfContents>>||
= Introduction =
Bugs relating to gwibber...
= How to file =
Useful for bug-filers and as a boiler-plate advice for triagers. This is the minimum information required for a bug report.
= Bug tags =
Bug tags specific to the package or area should be included here for reporters so they can tag their bug report. It will also be useful for triagers. The Bugs/Tags wiki page should then be modified to include these tags.
= Debugging procedure =
In depth debugging procedures for this particular package or subsystem. This usually is information about the log files to gather and what to look for in them.
= How to Triage =
Information that will facilitate the triaging of bugs for this package or subsystem. Remind triagers of the bug tags in use for this particular package.
== Stock Reply ==
A stock reply to be used for initial bug reports basically asking for the stuff in "How to file". The Bugs/Responses page should include this reply.
== How to Forward ==
In the event that the package or subsystem has an upstream bug tracker this section should contain detailed steps to forward a bug to that tracker. Some packages may just link to the general "How to Forward" page for another bug tracker like Gnome's bugzilla or freedesktop.org's bug tracker.
= Known bugs =
Description of known bug reports that may receive duplicates and how to recognise them. This information should be obtained by looking for bugs tagged as 'metabug'.
'''Open'''
||<rowbgcolor="#eeeeee"> '''Bug''' || '''Subject''' || '''Symptom''' ||
|| [[https://launchpad.net/bugs/8896|8896]] || The subject from LP || This bug can be identified by ... ||
'''Closed'''
||<rowbgcolor="#eeeeee"> '''Bug''' || '''Subject''' || '''Symptom''' ||
|| [[https://launchpad.net/bugs/8896|8896]] || The subject from LP || This bug can be identified by ... ||
= Non-bugs =
How to recognise common issues arising from hardware failures, common feature requests and other invalid bugs for this category. Advice how triage them and stock responses.
----
CategoryBugSquad
CategoryDebugging
More information about the Ubuntu-bugsquad
mailing list