Am Donnerstag, 29. September 2011, 13:25:49 schrieb Sebastian Kügler: > > It's frustrating for users submitting bug reports when an easily > > reproducible bug sits in the queue, without even a comment, for six > > > months. For the record, I'm referring to this bug report here: > This posting of bugreports to mailinglists is often seen as unnecessary, and > unfair since you're bringing attention to your pet bugs, which > disadvantages others' pet bugs. Please don't do it, your bug likely ends up > lower on developers' priority lists, and it sometimes causes bad blood (as > can be seen in recent history).
Ok, so if a user reports a bug and gets no answer for weeks, what should he do? Keep posting to the bug every few weeks, blog about it, private email to the dev, ask on IRC (which would not be much different than a mailinglist), post to the forums? If that makes no sense to start not caring about the bug. Not a good choice, is it? How is a user supposed to bring a bug to the devs' attention? Not at all? Just wait and see? How is that going to improve things? How is that going to add information to "low quality" bug reports? Votes don't change anything either, so they are not useful in order to bring attention to some bug. Lydia pointed out to find the "unloved" – and then do what if you are not supposed to name them in some place devs read? And as I pointed out already before, it's not like only "low quality" bug reports get no attention. Some people even add videos and test patches but still get no feedback. I think it is absolutely understandable that they get frustrated, as it is understandable that devs get frustrated about aggressive reporters. So IMHO if you want good bug reports you have to start giving good feedback. No feedback on bad reports will not improve that particular report and neither improve any of the following reports of the reporter. Neither will it enable him to help others on their reporting. So ignoring bad reports will increase the noise rather than decrease and it will thus increase devs' and users' frustration, i.e. you end-up with a lose-lose situation. > Even if you word it carefully, essentially your message is still saying that > a trivial to triage bug doesn't get the attention you think it should get. > That, however, is true for many bugs, sending reminders about them to > mailinglists is no solution, since it doesn't scale, nor does it give any > useful prioritization to developers. > > FWIW, I tend to other bugs, when I encounter this behaviour. If you would take a more positive approach to people who care enough to bring some bug they noticed for days/weeks to the devs attention (in a sensible wording of course!), then the latter is simply an opportunity for a wider community than devs reading bug reports to help the reporter gather more information to improve the report. Even posting a link to some wiki with examples of useful reports and a list of things to add/check would be more useful than ignoring a report for weeks and it would prevent frustration on both sides. Sven >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
