Skip to content
Snippets Groups Projects
Commit c927e7f6 authored by Andre Maroneze's avatar Andre Maroneze
Browse files

Merge branch 'content/blanchard/bug-reporting-less-aggressive' into 'master'

Less aggressive reporting guidelines

See merge request !31
parents e773ac5b 0f406185
No related branches found
No related tags found
1 merge request!31Less aggressive reporting guidelines
Pipeline #26072 passed
...@@ -26,10 +26,9 @@ Some advices to post your issue: ...@@ -26,10 +26,9 @@ Some advices to post your issue:
- If the bug report is not for a crash, include the **EXPECTED - If the bug report is not for a crash, include the **EXPECTED
BEHAVIOR** that you would have liked to see. BEHAVIOR** that you would have liked to see.
- Include the **OBTAINED BEHAVIOR** in enough detail that someone else - Include the **OBTAINED BEHAVIOR** in enough detail that someone else
(smart, but not mind-reading) can decide if they have reproduced can decide if they have reproduced your bug.
your bug.
- Include **HOW TO REPRODUCE** the issue. Provide everything necessary - Include **HOW TO REPRODUCE** the issue. Provide everything necessary
for a smart, but not mind-reading, human to reproduce the bug: input for someone else to reproduce the bug: input
files, command line used, sequence of actions. If your analysis files, command line used, sequence of actions. If your analysis
project depends on system headers, please use one of the two following project depends on system headers, please use one of the two following
options to be sure that: options to be sure that:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment