Timeline for Please reconsider closing bug-related questions if a workaround can be produced
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 16, 2016 at 3:54 | comment | added | Braiam | @JacobVlijm when I meant "vague" I really mean it, the kind of "I haz a bugz, send me teh fix, plox" kind of vague. Not even debugging information.... | |
| Aug 12, 2016 at 12:08 | comment | added | Jacob Vlijm | In case I answer questions with an unclear title, I pretty much always edit it. | |
| Aug 12, 2016 at 11:35 | comment | added | Braiam | @JacobVlijm people here tent to write the most vague, incomplete posts, which in turn makes them harder to find. Something difficult to find isn't useful. Bug reports force you to write something more coherent, include as much detail as possible (reproduction steps, tracebacks, etc.) and maintainers also make sure the bugs can be found and understood by editing. | |
| Aug 12, 2016 at 6:12 | comment | added | Jacob Vlijm | I don't see how workarounds, to be able to "live" with possible bugs, posted on the largest Ubuntu related support site would be dispersed over the internet. Despite bug reports, some of the issues we run into exist for a long time and seem hard to fix. I don't see any reason why we shouldn't improve the "quality of live" then to eliminate the effect of a bug. Even consider it an important part of the support we offer. | |
| Aug 12, 2016 at 6:08 | comment | added | Jacob Vlijm | I kind of expected you wouldn't agree :). However: "We are encouraged to vote on the current status of the post, not in the past nor future, but now". - It is not only the status of the post that determines if the issue is bug- related, but the information we have on the existence of a bug, the exact symptoms and the circumstances it appears with other users. | |
| Aug 11, 2016 at 23:52 | history | answered | Braiam | CC BY-SA 3.0 |