... | ... | @@ -61,9 +61,9 @@ Here is a check-list of things to cover in your description: |
|
|
|
|
|
## 3. The repro case
|
|
|
|
|
|
The absolutely key thing is that we must be able to reproduce the bug, the **repro case** ("repro" from "reproduction"). Without this, we are virtually helpless; we know there's a problem but often we can make no progress with fixing it.
|
|
|
The absolutely key thing is that we must be able to reproduce the bug, the **repro case**. Without this, we are largely helpless; we know there's a problem but often we can make no progress with fixing it.
|
|
|
|
|
|
Virtually helpless is not the same as complete helpless. Sometimes the bug manifests in some big code base, and or in a code base that you can't share. *It is still better to report the bug*, even if you can't offer a way to reproduce it. It may form part of a pattern with other bug reports, or someone may come up with good ideas for how you could narrow it down.
|
|
|
Largely helpless is not the same as complete helpless. Sometimes the bug manifests in some big code base, and or in a code base that you can't share. *It is still better to report the bug*, even if you can't offer a way to reproduce it. It may form part of a pattern with other bug reports, or someone may come up with good ideas for how you could narrow it down.
|
|
|
|
|
|
But we *really appreciate* effort to produce a repro case if you can:
|
|
|
|
... | ... | |