From 36e96fe8d5b459ddb1a9670bf681de5574c75caf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Maxime=20=E2=80=9Cpep=E2=80=9D=20Buquet?= Date: Sat, 6 Apr 2019 13:58:14 +0100 Subject: [PATCH] Remove 'Existing tools' section, move content down to Reproducibility MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Maxime “pep” Buquet --- .../posts/how-to-write-a-good-bug-report.md | 22 ++++++++----------- 1 file changed, 9 insertions(+), 13 deletions(-) diff --git a/content/posts/how-to-write-a-good-bug-report.md b/content/posts/how-to-write-a-good-bug-report.md index 92e9827..ef992c5 100644 --- a/content/posts/how-to-write-a-good-bug-report.md +++ b/content/posts/how-to-write-a-good-bug-report.md @@ -100,19 +100,6 @@ it makes it easier to isolate and track. People on the other side will be more capable at helping you with precise indications. It happens that you do not know, and in this case they might guide you and/or split the task for you. -### Existing tools - -Some applications already include automatic bug/crash reporting. For example -in [Firefox][crash-report] if you type "about:crashes" in the URL bar, you -will get a list of all crash reports that have been generated for you and sent -to Mozilla servers if you so chose at the time. These reports include data -useful for developers to find the cause of the crash. - -Often it is still good to have a bug report tracking a particular issue. In -this case you can link one or multiple related crash reports in it. - -[crash-report]: https://support.mozilla.org/en-US/kb/mozillacrashreporter - ### Reproducibility This part is about writing down the steps that lead you to the issue. These @@ -137,6 +124,13 @@ You can usually get all this information in the help menus of applications. ![][gnome-version]. +Some applications already include automatic bug/crash reporting. For example +in [Firefox][crash-report] if you type "about:crashes" in the URL bar, you +will get a list of all crash reports that have been generated for you and sent +to Mozilla servers if you so chose at the time. These reports include data +useful for developers to find the cause of the crash. + + As sysadmin, what I will be looking after is patterns, to try and identify what part of the system and software is responsible, where the issue lies and if there is code to fix for it, or if it is a configuration or user mistake. @@ -145,6 +139,8 @@ It often feels to me like playing detectives. The more patterns I observe, the more suspects I can cross off my list. It is rewarding to finally solve a complex case, but "boring" ones also help with mental health. +[crash-report]: https://support.mozilla.org/en-US/kb/mozillacrashreporter + ### What happens? Did anything happen at all?