Responses

Revision 1 as of 2009-10-29 00:44:28

Clear message

These are pre-made replies for dealing with commonly-reported bugs or for when you need to deal with a large amount of a certain type of bug. While these were designed to sound natural and non-canned, it always is nice for a bug reporter to get a uniquely-composed response to their bug, especially if the pre-made response does not exactly fit the situation. It gives the reporter assurance that the developer did indeed read the bug and does know what he is talking about. A list of general (and in some cases more canned-sounding) replied can be found at Bugs/Responses

To switch things up, it is also advised to switch you greeting/ending line. In the future we may have something automatic-ish to mix-n-match salutations and endings. Where "KDE program" is said in the responses, it is advisable to replace this with the program name.

Contents

  1. Upstream Bugs for KDE Packages
    1. Upstream Bugs of "Low" Importance
    2. Upstream Bugs of "Wishlist" Importance
    3. Upstream Bugs of "Wishlist" Importance
    4. Upstream Bugs of "Medium" Importance
    5. Upstream Bugs of "Medium" Importance Which Are Not SRU-able

Upstream Bugs for KDE Packages

Upstream bugs for KDE packages are handled specially in Kubuntu. Here are responses to fit most situations

Upstream Bugs of "Low" Importance

We send all low-importance upstream bugs on to KDE. Close these bugs as invalid, and reply with something similar to:

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

Upstream Bugs of "Wishlist" Importance

We send all low-importance upstream bugs on to KDE. Close these bugs as invalid, and reply with something similar to:

Hello,

Thanks for reporting this feature request! Unfortunately, at this time Kubuntu does not have the developer manpower needed to implement and maintain many features at the Kubuntu level. This wish would best be reported and tracked at https://bugs.kde.org, so that it can be implemented by the KDE developers themselves. Once implemented in KDE, it will be included in Kubuntu once the KDE version the feature is implemented in reaches Kubuntu.

Thanks!

Upstream Bugs of "Wishlist" Importance

We send all upstream wishlist items on to KDE. Close these bugs as invalid, and reply with something similar to:

Hi,

Thanks for reporting this feature request! Unfortunately, at this time Kubuntu does not have the developer manpower needed to implement and maintain many features at the Kubuntu level. This wish would best be reported and tracked at https://bugs.kde.org, so that it can be implemented by the KDE developers themselves. Once implemented in KDE, it will be included in Kubuntu once the KDE version the feature is implemented in reaches Kubuntu.

Thanks!

Upstream Bugs of "Medium" Importance

We keep bugs deemed as "Medium" tracked in Launchpad (2 or 3 duplicates or so for crashes, a bit of common sense helps here. When in doubt ask somebody in #kubuntu-devel). We want to upstream these ones and mark them as "Triaged".

Hello there!

We appreciate you reporting this bug! This is an issue with the KDE application itself of considerable severity. As such, it has been reported to KDE. You can track and make further comments at:

Thanks!

Upstream Bugs of "Medium" Importance Which Are Not SRU-able

Unfortunately we cannot SRU all upstream crashes that have fixes. Some fixes are just too intrusive. Detailed SRU guidelines can be found here. Hopefully we should not have too many of these, so it should be fine to track them until we release a fix. (For user visibility more than anything). Set 'em to fix committed and respond with something like:

Hi,

While this bug has been fixed by KDE, the fix is too intrustive to provide as a Stable Release Update (SRU). This is unfortunate, as this bug is not exactly nominal. Fortunately the fix will be made in the development version of Kubuntu 10.04, and will be available at 10.04's release.

Thanks for your patience and understanding