Responses

Differences between revisions 27 and 28
⇤ ← Revision 27 as of 2006-07-12 11:19:04 →
Size: 5001
Editor: i577B2ED9
Comment:
← Revision 28 as of 2006-07-21 10:08:12 → ⇥
Size: 4947
Editor: 83-216-156-196
Comment: improve grammar and remove a line that makes little sense
Deletions are marked like this. Additions are marked like this.
Line 113: Line 113:
Thanks for your comments. This does not appear to be bug related. We
appreciate the difficulties you are facing, however it might make more
sense to raise your question at http://launchpad.net/support.

I will close the bug here and thank you for taking care.		 Thanks for your comments. This does not appear to be a bug report as
such. We appreciate the difficulties you are facing, but it would
make more sense to raise your question at
http://launchpad.net/support.

Standard Responses

The following standard responses can be used when replying to bug reports:

If the bug is not described well

Thanks for taking the time to report this bug. Unfortunately, we are
not able to fix and find the bug because your description of the bug
didn't have enough information in it.  You may find it helpful to read
"How to report bugs effectively", 
        http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.
We'd be grateful if you would then provide a more complete description
of the problem.

Debugging procedures for certain types of problems can be found at
http://wiki.ubuntu.com/DebuggingProcedures

or in case of aged NeedsInfo bugs 

Your bug lacks information we would need to investigate further. We
are now going to close the bug - please reopen if you have more
information at hand.

If the bug is in an obsolete version of the application

Thanks for the bug report. However, the version you are using is no
longer maintained.

Please upgrade to the most recent version, and open a new bug if the
problem persists.

If the bug has no back trace

Thanks for your bug report. Could you please try to obtain a
backtrace by following the instructions on
       http://wiki.ubuntu.com/DebuggingProgramCrash.
This will greatly aid us in tracking down your problem.

If the bug is a duplicate

Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but please feel free to report
any further bugs which you find.

OR 

Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but the maintainers do need
more information to fix the bug. Could you please answer the questions
which are in the other report?

If the bug report needs to go upstream

Thanks for your bug report. This particular bug has been filed
with the developers of the software. You can track this and make
comments here:

If the bug is fixed in Dapper but still exist in Breezy

If the package can be backported: 

Thanks for the bug report.

I'm closing this bug because it has been fixed in Dapper.

If you need a fix for this bug in Breezy, please follow the
instructions in the "How to request new packages" section of the
Backports wiki page:
        https://wiki.ubuntu.com/UbuntuBackports

If not: 

Thanks for the bug report.

I'm closing this bug because it has been fixed in Dapper.

It won't be fixed in Breezy since this bug doesn't fit backports
requirements. See https://wiki.ubuntu.com/UbuntuBackports for
more information.

If people are not respecting the Code of Conduct

Thanks for your bug report. To maintain a respectful atmosphere,
please be  sure to follow http://www.ubuntu.com/community/conduct/
Conversations in bugs are done by humans, so please bear this in
mind.

If the bug is a feature request

Thanks for your report. Your idea might get more attention and have
the possibility of being implemented if you would submit a
specification for this.

You should first check whether it already exists at the Ubuntu specs
page (https://launchpad.net/distros/ubuntu/+specs) in Launchpad. If
that is the case, feel free to contact the drafter of that spec about
your comments/suggestions. Otherwise you can start writing a spec
following the steps described in
        https://wiki.ubuntu.com/FeatureSpecifications.

If the bug is a support request

Thanks for your comments. This does not appear to be a bug report as
such. We appreciate the difficulties you are facing, but it would
make more sense to raise your question at
http://launchpad.net/support.

If the bug is a suggestion for changing defaults

Thanks for your comment. The changes you are requesting require more
discussion and should rather be done on an appropriate mailing list or
forum.

http://www.ubuntu.com/community/forums/ might be a good start.

If the bug points out that a translation is wrong

Thanks for your comment. Ubuntu gets its translations from
http://launchpad.net/rosetta. This is the place where translation teams
actively work on making Ubuntu more useful in their language. If you want
to change a certain text, Rosetta is the right place for it.

If it's a packaging request of new software

Thanks for your suggestion. This is not the right place to request new
software. Please add your suggestion to
        http://wiki.ubuntu.com/UniverseCandidates.

Other projects have standard responses as well:

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

Bugs/Responses (last edited 2025-09-18 13:12:42 by sally-makin)