User:Grundleborg/Bugsquad Canned Responses: Difference between revisions

From KDE TechBase
Line 1: Line 1:
==Bugsquad Proposed Canned Responses==
==Bugsquad Proposed Canned Responses==
This page contains a selection of canned responses that I am proposing as guidelines/example responses to bug-triagers. They are not meant to be taken as the law for responding to bugs, but there is no harm in using them as templates when replying to applicable bugs (particularly if you are someone prone to being very blunt/impatient with bug reporters ;)).
This page contains a selection of canned responses that I am proposing as guidelines/example responses to bug-triagers. They are not meant to be taken as the law for responding to bugs, but there is no harm in using them as templates when replying to applicable bugs.


===Closing report due to being non-reproducible in latest released version===
===Closing report due to being non-reproducible in latest released version===

Revision as of 14:45, 29 January 2009

Bugsquad Proposed Canned Responses

This page contains a selection of canned responses that I am proposing as guidelines/example responses to bug-triagers. They are not meant to be taken as the law for responding to bugs, but there is no harm in using them as templates when replying to applicable bugs.

Closing report due to being non-reproducible in latest released version

Hi <name>. Thanks for taking the time to report this bug. It seems to be fixed in KDE <latest-released-version>, so I am closing this report. However, if you still continue to experience this bug in KDE <latest-released-version>, please let us know by reopening the report and leaving a comment and we will attempt to investigate it again.

Closing report due to being non-reproducible in current svn

Hi <name>. Thanks for taking the time to report this bug. It seems to be fixed in the current svn trunk of KDE, so I am closing this report. The fix for this bug will be included in KDE <next-release-version>. However, if you still continue to experience this bug in svn trunk or KDE <next-release-version>, please let us know by reopening the report and leaving a comment and we will attempt to investigate it again.