Timeline for Responsibility to reproduce bugs
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2013 at 8:18 | comment | added | isntn | Hi, Down voting pushes answer down in the list. Instead of down voting, you could up vote answers you find better. That way, you are fetching good answer up in the list. If answer is just another possible way to deal with question, you should NOT down vote. It is unfortunate that protest looks 'whining' and 'confusion' to you. Some readers will not even read down voted answer. I do not think my answer deserves that. Whoever has down-voted does not appreciate that I had put effort to answer and down voting 'different-from-expectation' answer does not encourage anybody. | |
| Jun 10, 2013 at 19:25 | comment | added | Dan Is Fiddling By Firelight | You appear confused about the proper use of voting, and whiing about it is unlikely to help your case. Downvotes are the accepted way to say "I think this is a bad answer". Offensive language should be dealt with not (solely) via down voting, but by either editing it out or flagging depending on if the rest of the answer is useful. An out of context an answer could be handled either way depending on how egregious it is. | |
| Jun 10, 2013 at 19:03 | comment | added | Joshua Drake | @Andy In some positions it is corporate policy that bugs are not accepted without an automated test. | |
| Jun 10, 2013 at 18:00 | comment | added | Dan Is Fiddling By Firelight | I didn't vote down; but I stand by my characterization that whatever excuses the other developer made what he did amounts to ignoring the issue. | |
| Jun 10, 2013 at 17:51 | comment | added | isntn | Hi, If you do NOT find my answer good enough, do not up-vote. I have neither used bad language nor answered out of context. I request you to remove down votes. | |
| Jun 10, 2013 at 17:31 | comment | added | isntn | @DanNeely: He is not ignoring, he is claiming that reporter has to do something more - which is not possible to do for reporter. And reporter has to communicate back! I have also suggested to involve authority, as this may get down to that. | |
| Jun 10, 2013 at 17:29 | comment | added | isntn | I find -ve marking little too harsh! @Andy: you are right. But you need to keep communication rolling! and I just suggested a way. | |
| Jun 10, 2013 at 17:28 | history | edited | isntn | CC BY-SA 3.0 | Just structuring it better... |
| Jun 10, 2013 at 17:15 | comment | added | Dan Is Fiddling By Firelight | If the other developer is ignoring bug reports from someone there's virtually zero chance of him responding favorably to a request for a major refactoring. Also, not all types of problem are readily reproducible via unit testing: programmers.stackexchange.com/questions/196105/… | |
| Jun 10, 2013 at 17:13 | comment | added | Andy | It's not the OPs responsibility to create the unit test for the library maintainer. | |
| Jun 10, 2013 at 16:18 | history | answered | isntn | CC BY-SA 3.0 |