Rework 'why report bugs'
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
parent
63ad6b86fa
commit
7405866547
1 changed files with 8 additions and 7 deletions
|
@ -44,16 +44,17 @@ able to do with the information.
|
||||||
|
|
||||||
Why would you need to write a bug report/file a ticket in the first place?
|
Why would you need to write a bug report/file a ticket in the first place?
|
||||||
|
|
||||||
What first comes to mind is that sysadmins might not know you have issues. And
|
What first comes to mind is that sysadmins might not know you have issues.
|
||||||
it would probably be beneficial for you, and possibly others, that you tell
|
And it would probably be beneficial for you, and possibly others, that you
|
||||||
them.
|
tell them.
|
||||||
|
|
||||||
A ticket is also helpful to be able to track the progress. This might help
|
A ticket is also helpful to be able to track the progress. This will also
|
||||||
future you encountering the same issue again be able to fix it yourself, or to
|
help other users encountering the same issue and allow them to fix it
|
||||||
refer to it later on.
|
themselves, or allow you to refer to it in a follow-up ticket, ("You know,
|
||||||
|
_that_ bug I talked to you about six months ago.")
|
||||||
|
|
||||||
It is also helpful to track the resolution of an issue, ("What happened to my
|
It is also helpful to track the resolution of an issue, ("What happened to my
|
||||||
issue?"). Some issues will get fixed and closed, some will not, some might be
|
issue?"). Some issues will get fixed and closed, some will not, some might be
|
||||||
closed for _reasons_, without getting fixed.
|
closed for _reasons_, without getting fixed.
|
||||||
|
|
||||||
## Why write a good bug report?
|
## Why write a good bug report?
|
||||||
|
|
Loading…
Reference in a new issue