[gst-devel] Submitting a Bug

Benjamin Otte in7y118 at public.uni-hamburg.de
Fri Jan 7 05:41:04 CET 2005

On Thu, 6 Jan 2005, Maciej Katafiasz wrote:

> Dnia 06-01-2005, czw o godzinie 15:06 -0500, Larry Berlinski napisa³:
> > What is the process for submitting a bug? Is it only necessary to
> > gather the documentation and post it to bugzilla, and someone will see
> > it, prioritize it and assign it??? or should it first go through the
> > developer's list then into bugzilla?
> You should never assign bugs to anyone besides yourself, it will be done
> by someone who intends to take the bug over. Other than that, it's
> pretty simple really, just do your best :). Gather as much relevant info
> as you can, then file a bug, if something more is needed, it will be
> commented on and you'll get email from bugzilla-daemon with that
> comment. If you are particularly unsure about the issue, or think it's
> harder than usual, feel free to drop by IRC channel or mailing list, we
> will help. But except for very tricky ones, just filing it best you can
> is enough, it will get corrected later on when the need arises. Only try
> to be clear, and don't guess if bugzilla doesn't require that (ie, it's
> OK to guess the component, but it's not okay to randomly guess about
> SEGV cause if you don't know). It's always better to have scarce, but
> readable and definitely true report, than elaborate but unclear or
> untrue one that will only confuse people. And at the very least, even if
> you know nothing other than that bug exists, file it anyway. Bug that's
> filed, even badly, has about infinity more chances to be fixed than one
> that isn't :)
To cut a long story short:
The more information about a bug exists, the better the chances that it is

Benjamin :)

More information about the gstreamer-devel mailing list