LucidBugTriagePolicy

Differences between revisions 4 and 5
⇤ ← Revision 4 as of 2009-10-24 20:53:15 →
Size: 1172
Editor: 84-119-15-125
Comment:
← Revision 5 as of 2009-10-24 21:04:34 → ⇥
Size: 2020
Editor: d-65-175-172-80
Comment:
Deletions are marked like this. Additions are marked like this.
Line 19: Line 19:
* Richard is developer... * Richard is developer. Richard wishes to be able to at any given time see what needs to be done to improve Kubuntu's packages. With a manageable list that tracks only packaging bugs and more serious upstream bugs, he can easily see what needs to be done without wading through hundreds of low priority upstream bugs, and help to resolve these issues more quickly.
Line 21: Line 21:
* Jonathan is bug triager... * Jonathan is bug triager. Jonathan wishes to not have to maintain drivers to interface his brain to the Launchpad API. With a bug policy that directs upstream bugs upstream, Jonathan is happy that he can more easily and efficiently prioritize and confirm the now-more-manageable amount of bugs in Launchpad.
Line 23: Line 23:
* Stephan is upstream developer... * Stephan is upstream developer. Stephan likes to be able to receive bug reports from users with issues. With bugs going straight to upstream, Stephan can deal with these issues in a more timely manner as well as engage with the user for more effective debugging.

Summary

This specification defines what the revised bug triage policy for Kubuntu versions >= should look like.

Rationale

Kubuntu tracked packages currently do get way to many bug reports, compared to the amount of people doing active bug triage. It is necessary to revise the policy of bug triage so that bug triage and bug management can be more efficient given the circumstances.

Scope and Use Cases

Use Cases

* Alex is Kubuntu user. From time to time he reports bugs against KDE packages at launchpad.net, his reports get processed quickly and resolved in the upcoming Kubuntu release. Important issues get resolved more quickly. Alex is happy to contribute something to the FLOSS community and sleeps well at night.

* Richard is developer. Richard wishes to be able to at any given time see what needs to be done to improve Kubuntu's packages. With a manageable list that tracks only packaging bugs and more serious upstream bugs, he can easily see what needs to be done without wading through hundreds of low priority upstream bugs, and help to resolve these issues more quickly.

* Jonathan is bug triager. Jonathan wishes to not have to maintain drivers to interface his brain to the Launchpad API. With a bug policy that directs upstream bugs upstream, Jonathan is happy that he can more easily and efficiently prioritize and confirm the now-more-manageable amount of bugs in Launchpad.

* Stephan is upstream developer. Stephan likes to be able to receive bug reports from users with issues. With bugs going straight to upstream, Stephan can deal with these issues in a more timely manner as well as engage with the user for more effective debugging.

Implementation Plan

Implementation

CategorySpec

Kubuntu/Specs/LucidBugTriagePolicy (last edited 2009-11-18 22:15:50 by 63)