CommonTasks

Differences between revisions 49 and 50
Revision 49 as of 2007-07-06 15:33:27
Size: 8251
Editor: c-24-21-231-115
Comment: General overhaul
Revision 50 as of 2007-07-20 04:14:41
Size: 4413
Editor: c-24-21-231-115
Comment: Setup Include for MarkingDuplicate page
Deletions are marked like this. Additions are marked like this.
Line 45: Line 45:

== Finding Duplicates ==

Finding duplicates of bugs is a very valuable contribution in the Bug community. Users sometimes don't know how to check if the same bug has already been filed, or it is hard for them to determine if their bug is the same as another. Weeding out simple '''ME TOO''' messages and aggregating information in one place is crucial to the process of fixing a bug.

There are quite a few measures you can take to assist with this aspect, one way is to search for bugs filed for the same component, also try to rephrase your search, and concentrate on ''actions'' and ''words that describe'' the items involved to reproduce this crash.

Examples:

 * Easy ones:
  * [http://bugzilla.ubuntu.com/show_bug.cgi?id=18808 DAAP support] is a duplicate of
   * [http://bugzilla.ubuntu.com/show_bug.cgi?id=18733 please enable daap]
 * More difficult ones:
  * [http://bugzilla.ubuntu.com/show_bug.cgi?id=17858 plug:spdif on emu10k1 gone after breezy upgrade] is a duplicate of
   * [http://bugzilla.ubuntu.com/show_bug.cgi?id=15585 Muted sound after dist-upgrade from Hoary to Breezy]
   
If you can't find it in the list of open bugs, you could try to find it in the list of closed (Invalid or Won't Fix) ones. Don't feel discouraged, if you don't find duplicates fast in the beginning, after some time you will get to know the usual suspects, and learn how to more easily identify them.

Please check any appropriate items in DebuggingProcedures before marking bugs as duplicates, as in some cases it is not as obvious as it might seem.

''Note:'' If you encounter a bug that has a summary that is not descriptive of the issue, rephrase it, so people find it more easily. This may help reporters find their bug.
[[Include(Bugs/MarkingDuplicate)]]
Line 72: Line 52:
== Managing Status == [[Include(Bugs/Status)]]
Line 74: Line 54:
As a reporter you usually don't have to take care of statuses. As a bug triager or developer it's an important tool to categorize bugs and have a good overview over the state of packages and software.

Here's a brief list and explanation of the various statuses:

 * '''New''':
  * Bugs start with this status,
  * Bugs marked {{{New}}} sometimes lack information and most of them are untriaged
 * '''Incomplete''':
  * If you have to ask the reporter questions, please set the bug to {{{Incomplete}}}
  * Ask the submitter to provide any necessary information in a comment, and make sure you subscribe to the bug so you will get the response.
  * a regular task for {{{Incomplete}}} bugs is to ask back, if there are no answers and after a reasonable stage (about a month), close them (as {{{Inavild}}} ) saying "If you have more information on this bug, please reopen."
 * '''Invalid''':
  * Bugs marked as {{{Invalid}}} are closed
  * Be sure to triple-check a bug before you reject it.
 * '''Confirmed''':
  * Bugs that are trivially reproduced, or have enough information attached that a developer can fix it.
  * {{{Confirmed}}} bugs require confirmation from '''someone other than the original reporter'''
  * This helps ensure that the bug is applicable to Ubuntu in general, and not a problem with the reporter's system, therefore...
  * Please don't confirm your own bugs!
 * '''In Progress''':
  * If you are working on fixing a bug, set it to {{{In Progress}}} so people know what's going on
  * Only the person to whom the bug is assigned should set this status
 * '''Fix Committed''':
  * Means for upstream projects, that the fix is in CVS/SVN/bzr or commited to some place
  * Means for package maintainers, that the changes are pending and to be uploaded soon (it's what PENDINGUPLOAD was in Bugzilla)
 * '''Fix Released''':
  * Means for upstream projects, that a release tarball was announced and is publically available
  * Means for package maintainers, that a fix was uploaded
   * Please don't be hesitant to add a changelog as a comment, so people know what to look out for

== Managing Importance ==

Please see ["Bugs/Importance"].
[[Include(Bugs/Importance)]]
Line 114: Line 62:
In many cases bugs reported in earlier versions are still open in our BTS. They may have been fixed upstream without it being noted in Malone or the design may have changed so that the issue is no longer relevant. If the bug does not represent a security issue or is otherwise critical, it is very unlikely that the fix will be back-ported to older versions of Ubuntu. When it is fixed in the development branch it is therefore most appropriate to mark it 'Fix Released'. This helps clear the BTS for old cruft. In many cases bugs reported in earlier versions are still open in our bug tracking system. They may have been fixed upstream without it being noted in Malone or the design may have changed so that the issue is no longer relevant. If the bug does not represent a security issue or is otherwise critical, it is very unlikely that the fix will be back-ported to older versions of Ubuntu. When it is fixed in the development branch it is therefore most appropriate to mark it 'Fix Released'. This helps clear the bug tracking system for old cruft.

Overview

TableOfContents

The proper source package

Assigning bugs to packages helps direct bug reports to the developer(s) most likely to be able to help. By ensuring that this information is accurate, you can increase the chances of the bug being fixed promptly. Often, it is unclear which package contains the bug, and in these cases it is appropriate to file the bug in Ubuntu. If a bug is assigned to a package which is clearly not correct, and you don't know the correct package, change it to Ubuntu. Some hints on finding the right package can be found in ["Bugs/FindRightPackage"].

The correct package for bugs in the Linux kernel is dependent upon the release of Ubuntu being used.

  • For Dapper (6.06) the correct package is linux-source-2.6.15
  • For Edgy (6.10) the correct package is linux-source-2.6.17
  • For Feisty (7.04) the correct package is linux-source-2.6.20
  • For Gutsy (7.10) the correct package is linux-source-2.6.22

Confirming problems

If a bug is marked as New, it is helpful for you to try to reproduce the problem, and record the results in Malone. If you are able to confirm the problem, you may change the status to Confirmed. If you are unable to confirm the problem, that is also useful information which should be recorded in a comment. When confirming the bug be sure to indicate which version of the package you used. One way to get the package version is via 'dpkg -l $pkgname' where $pkgname is the name of the package you are testing. Do not confirm your own bugs - confirmation is required from someone other than the original reporter.

Forwarding bugs upstream

You should forward bugs to the authors of the software (upstream), if

  • you made sure that the bug doesn't occur because of Ubuntu related changes,
  • the bug report is complete.

To learn how to do this, please consult [https://wiki.ubuntu.com/Bugs/HowToTriage#head-ab0eb9d7731fa877b5fc866eedc4c312dab50ee7 The Forwarding section in the How to Triage Page].

How to deal with Feature Requests

If you feel that the bug reported is a non-trivial feature request disguised as a bug report, please introduce the reporter gently to the Specification Process we have. Be sure to mention the following specification resources; FeatureSpecifications, SpecSpec, ["SpecTemplate"] and http://launchpad.net/specs

How to deal with Support Requests

If you feel that the bug reported is a support request disguised as a bug report, please gently introduce the reporter to the Support Tracker located at http://answers.launchpad.net/ubuntu/ .

How to deal with suggestions for changing defaults

If you feel that the bug reported is a suggestion for changing defaults disguised as a bug report, please kindly reroute the discussion to an appropriate mailing list or a discussion forum. If this has already been discussed and rejected, explain the reasons to the user and direct them to the corresponding discussion for further suggestions/comments.

Include(Bugs/MarkingDuplicate)

Reminder of the Code of Conduct

Note that the Code of Conduct applies to conversations in bug reports too. So if you observe people being disrespectful, please direct them to http://www.ubuntu.com/community/conduct

Include(Bugs/Status)

Include(Bugs/Importance)

Milestone

Don't change this field unless specifically instructed by a developer. In particular, do NOT use this field to record the release of Ubuntu in which the bug was observed: that is not its purpose! It is used by the release team when there is a reason to address the bug in a specific milestone release.

Old Bugs

In many cases bugs reported in earlier versions are still open in our bug tracking system. They may have been fixed upstream without it being noted in Malone or the design may have changed so that the issue is no longer relevant. If the bug does not represent a security issue or is otherwise critical, it is very unlikely that the fix will be back-ported to older versions of Ubuntu. When it is fixed in the development branch it is therefore most appropriate to mark it 'Fix Released'. This helps clear the bug tracking system for old cruft.


Back to ["HelpingWithBugs"].BRBR [:CategoryBugSquad]

Bugs/CommonTasks (last edited 2011-06-15 18:35:14 by c-98-246-63-231)