CommonTasks

Differences between revisions 1 and 6 (spanning 5 versions)
⇤ ← Revision 1 as of 2005-11-02 20:13:35 →
Size: 1209
Editor: 209
Comment:
← Revision 6 as of 2005-11-02 21:25:10 → ⇥
Size: 2593
Editor: 209
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== Overview ==

 * [#forwarding Forwarding bugs upstream]
 * [#feature How to Deal with Feature Requests]
 * [#support How to deal with Support Requests]
 * [#duplicates Finding Duplicates]

[[Anchor(forwarding)]]
== Forwarding bugs upstream ==

You can forward bugs upstream, if
 * you made sure, that the bug doesn't occur because of Ubuntu related changes
 * the change too hard to fix for yourself and anyone else in the team

If you do this, be sure to
 * include all the necessary information, like
  * how to reproduce
  * which version is used (which version of dependend libraries, if the bug indicates problems there)
  * who reported it
  * where the whole conversation is to be found
 * create a bug watch in Malone for this

[[Anchor(feature)]]
== How to Deal with Feature Requests ==

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

[[Anchor(support)]]
== How to deal with Support Requests ==

If you feel that the bug reported is a support request disguised as bug report, please introduce the reporter gently to the Support Trackker we have. Be sure to mention http://launchpad.net/support

[[Anchor(duplicates)]]
== Finding Duplicates ==
Line 13: Line 48:
  * [http://bugzilla.ubuntu.com/show_bug.cgi?id=17858 plug:spdif on emu10k1 gone after breezy upgrade]   * [http://bugzilla.ubuntu.com/show_bug.cgi?id=17858 plug:spdif on emu10k1 gone after breezy upgrade] is a duplicate of

Overview

  • [#forwarding Forwarding bugs upstream]
  • [#feature How to Deal with Feature Requests]
  • [#support How to deal with Support Requests]
  • [#duplicates Finding Duplicates]

Anchor(forwarding)

Forwarding bugs upstream

You can forward bugs upstream, if

  • you made sure, that the bug doesn't occur because of Ubuntu related changes
  • the change too hard to fix for yourself and anyone else in the team

If you do this, be sure to

  • include all the necessary information, like
    • how to reproduce
    • which version is used (which version of dependend libraries, if the bug indicates problems there)
    • who reported it
    • where the whole conversation is to be found
  • create a bug watch in Malone for this

Anchor(feature)

How to Deal with Feature Requests

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

Anchor(support)

How to deal with Support Requests

If you feel that the bug reported is a support request disguised as bug report, please introduce the reporter gently to the Support Trackker we have. Be sure to mention http://launchpad.net/support

Anchor(duplicates)

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 was already filed, and sometimes don't care. To weed out simple ME TOO messages and aggregate information in one place is crucial in the process of fixing a bug.

There are quite some measures you can take to help out with this specifically.

Look up bugs for the same component. Try to rephrase your search concentrate on actions an words that describe the items involved to reproduce this crash.

Examples:

If you can't find it in the list of open bugs, you could try to find it in the list of closed ones. Don't feel discouraged, if you don't find duplicates fast in the beginning, after some time you will know the usual suspects.

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