[mythtv-users] How to make a good bug report?

[Isaac Richards]

On Thursday 08 July 2004 10:24 pm, John Goerzen wrote:
> Now, there are a bunch of problems with this:
>
> 1. Just because a description is poor does not mean that a bug does not
>    exist.  Before closing the bug, you should at least ask for the
>    information you need, ESPECIALLY since the bug writing guidelines
>    do not spell out what information you need.

Nope -- If the description is poor and I cannot reproduce it, the bug does not 
exist.

> 2. This is no way to treat people that are trying to improve MythTV.
>    It's only a way to make people leave the project.
>
>    Many users that report bugs are future developers, remember.

Hah.

> 3. The person closing it didn't describe what information was missing.

Steps so that anyone can reproduce it?

> 4. The bug report included exact steps necessary to reproduce the bug
>    and a precise description of th eproblem.

"Observe flickering" is not a valid step in how to reproduce the bug.

> Can we please be less antagonistic towards people that are trying to
> help?
>
> And why don't you post what info you need in the bug writing guidelines
> rather than yelling at people that submit bugs, or worse, close reports
> of real bugs because you don't give a damn?
>
> Just what info *DO* developers want for bugs in the frontend?  backend?
> transcode?  Other modules?

What I _don't_ want is random people who don't know what they're doing from 
the -users list using the bugzilla yet.  I didn't announce it here or the web 
page for a _reason_.

Isaac