Timeline for What should be reported when a bug only happens 50% of the time?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 3, 2018 at 0:57 | vote | accept | lonious | ||
| Jul 4, 2017 at 3:26 | comment | added | corsiKa♦ | As a former developer, can you just give us a bug report that only shows up in the queue of things to work on 50% of the time? I think that'd be a lot more appropriate. | |
| Jul 2, 2017 at 0:08 | comment | added | R.. GitHub STOP HELPING ICE | Not just "still a bug". Other things equal, a bug that only happens X % of the time is 100/X times as bad as one that always happens. | |
| S Jul 1, 2017 at 14:17 | history | suggested | Peter Mortensen | CC BY-SA 3.0 |
Copy edited. (its = possessive, it's = "it is" or "it has". See for example <http://www.wikihow.com/Use-Its-and-It%27s>.)
|
| Jul 1, 2017 at 13:53 | review | Suggested edits | |||
| S Jul 1, 2017 at 14:17 | |||||
| Jun 30, 2017 at 23:32 | comment | added | alecxe | @Mark that was a fun read - have not yet encountered this story before. Thanks for posting the link! | |
| Jun 30, 2017 at 23:02 | comment | added | Mark | @Wildcard, the inability to send an email more than 500 miles. | |
| Jun 30, 2017 at 20:03 | comment | added | Wildcard | Also, caching. Cronjobs. Timeouts. Date changes. Second hand marker (like a bug that only surfaces if the start and end of a job occur in different minutes, so if you start at :59 you see it but if you start at :07 you don't). More caching. Failure to cache. Should you blame caching? | |
| Jun 30, 2017 at 1:37 | history | edited | alecxe | CC BY-SA 3.0 |
added 43 characters in body
|
| Jun 30, 2017 at 1:15 | history | edited | alecxe | CC BY-SA 3.0 |
added 125 characters in body
|
| Jun 30, 2017 at 1:09 | history | answered | alecxe | CC BY-SA 3.0 |