[gst-devel] Submitting a Bug

Maciej Katafiasz ml at mathrick.org
Thu Jan 6 14:43:09 CET 2005

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 :)

Oh, and check out FAQ:

> Live Long and Prosper

Sure, will do :)


PS. Docs-wranglers, maybe add that to FAQ section? I'm not touching docs
since last I checked they didn't even build on my Debian box...

Maciej Katafiasz <ml at mathrick.org>

More information about the gstreamer-devel mailing list