Timeline for How to respond to requests to retest, in hope that the bug is gone?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 15, 2019 at 12:09 | comment | added | Michael Stahl | Of course we have "not reproducible"; but as @Mars indicated, it's something else. It means the bug is not reproducible on the same setup and version that was reported. My question is about cases where the bug is gone when trying to reproduce on a new build. | |
| Nov 15, 2019 at 0:18 | comment | added | Mars | I'd make a distinction between "Not reproducible" and "No longer reproducible". Not reproducible means Testing did something weird and Dev can't confirm the bug | |
| Nov 15, 2019 at 0:17 | comment | added | Mars |
This. Closed: Fix (#Commit Num) and Closed: Fix (No longer reproducible)
|
|
| Nov 14, 2019 at 18:30 | review | First posts | |||
| Nov 14, 2019 at 21:21 | |||||
| Nov 14, 2019 at 18:29 | history | answered | Beanluc | CC BY-SA 4.0 |