Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
tails
tails
Commits
1d6d85b7
Commit
1d6d85b7
authored
Apr 07, 2013
by
Tails developers
Browse files
Add a summary of 'How to Report Bugs Effectively'
parent
65a87809
Changes
1
Hide whitespace changes
Inline
Side-by-side
wiki/src/doc/first_steps/bug_reporting.mdwn
View file @
1d6d85b7
...
...
@@ -25,7 +25,17 @@ Have a look at:
How to write a useful bug report
================================
Please read at least the _Summary_ section of the great [How to Report Bugs
- The first aim of a bug report is to **let the developers reproduce the
failure**. Give them detailed instructions so that they can make it fail for
themselves.
- If that is not possible, try to **describe what went wrong in detail**.
Write down the error messages, especially if they have numbers in.
- Write **clearly and be precise**. Say what you mean, and make sure it
cannot be misinterpreted.
- Be ready to provide extra information if the developers need it. If they
did not need it, they would not be asking for it.
You can also refer to the great [How to Report Bugs
Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html), by
Simon Tatham.
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment