ReportingBugs

Differences between revisions 8 and 9
⇤ ← Revision 8 as of 2006-01-12 09:37:05 →
Size: 3114
Editor: i577B06D0
Comment:
← Revision 9 as of 2006-01-12 09:56:03 → ⇥
Size: 2430
Editor: 203-206-46-153
Comment: removed all references to Bugzilla
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
Software contains flaws, called bugs. To manage them, Ubuntu currently uses two bug tracking systems: Software contains flaws, called bugs. To manage them, Ubuntu uses the [ttps://launchpad.net/malone Malone] bug tracking system.
Line 6: Line 6:
== Bug trackers ==
=== Bugzilla ===
Bugzilla is a bug tracker developed by the Mozilla Project. It is used by Ubuntu for tracking all of the bugs in packages which are supported (in {{{main}}} and {{{restricted}}})		 == Malone ==
Line 10: Line 8:
The Ubuntu Bugzilla can be found here: http://bugzilla.ubuntu.com/

=== Malone ===

Malone is a new bug tracker created as part of the Launchpad architecture. Malone is currently used to track all bug for non-supported packages ({{{universe}}} and {{{multiverse}}})

Malone can be found here: https://launchpad.net/distros/ubuntu/+bugs		 Malone is a new bug tracker created as part of the Launchpad architecture. Malone is used to track all bugs for Ubuntu and bugs for packages from other distributions.
Line 19: Line 11:

In order to start using either Bugzilla or Malone, you need an account.

=== Bugzilla ===

To create an account in Bugzilla, go [https://bugzilla.ubuntu.com/createaccount.cgi here]

=== Malone ===
Line 32: Line 16:
Once you have an account on one (or both) of the bug trackers, time to ask the critical questions. The first thing you should do is look at the following guides about when to file a bug or not. The first thing you look are the following guides about deciding to file a bug or not.
Line 51: Line 35:
So your bug is an actual bug. The first thing you should do is search for it being already reported. If it is not, then click on the '''New'''  link for Bugzilla or the '''Report a bug''' for Malone. Try and fill out a useful summary, select which program it happened in. If you do not know, take a guess or ask someone. Then fill out the description with as much information as you can. It is better to have more information that too little. Once you have filed out the package name, summary and description, click on submit. Unless you are experienced, it is best if you leave the other fields blank or with their default information. You are now done. So your bug is an actual bug. The first thing you should do is search for it being already reported. If it is not, then click on the '''File a Bug on a Package''' link within Malone. Try and fill out a useful summary, select which program it happened in. If you do not know, take a guess or ask someone. Then fill out the description with as much information as you can. It is better to have more information that too little. Once you have filed out the package name, summary and description, click on submit. Unless you are experienced, it is best if you leave the other fields blank or with their default information. You are now done.

Software contains flaws, called bugs. To manage them, Ubuntu uses the [ttps://launchpad.net/malone Malone] bug tracking system.

If you want to help fixing bugs, please see HelpingWithBugs

Malone

Malone is a new bug tracker created as part of the Launchpad architecture. Malone is used to track all bugs for Ubuntu and bugs for packages from other distributions.

Getting started

Malone uses the Launchpad login, which is the same as this wiki. To create a Launchpad account, go [https://launchpad.net/distros/ubuntu/+bugs/+login here]

Filing Bugs

The first thing you look are the following guides about deciding to file a bug or not.

If you need help with debugging a problem, see ["Debugging"]

If you need help with actually filing the bug, http://www.chiark.greenend.org.uk/~sgtatham/bugs.html has quite a lot of information on how to do it properly.

When to file a bug

  • You can repeat the problem
  • It is not a feature of the program

When to not file a bug

Actually filing the bug

So your bug is an actual bug. The first thing you should do is search for it being already reported. If it is not, then click on the File a Bug on a Package link within Malone. Try and fill out a useful summary, select which program it happened in. If you do not know, take a guess or ask someone. Then fill out the description with as much information as you can. It is better to have more information that too little. Once you have filed out the package name, summary and description, click on submit. Unless you are experienced, it is best if you leave the other fields blank or with their default information. You are now done.

Bug triage

Bug triage is the act of cleaning up old bugs, solving some, and closing those which are incorrectly filed. Information on bug triage can be found at HelpingWithBugs.

CategoryDocumentation

ReportingBugs (last edited 2008-08-06 16:33:09 by localhost)