| From David Timms <dtimms@...>
| Thu, 29 Jul 2010 22:54:40 +1000
| Subject: [Audacity-devel] issues in audacity
> Hi, I am the currently maintainer of audacity in Fedora (and rpmfusion).
> Since Fedora enabled abrt for capture of debugging information, we ave
> received quite a few bug reports. While some have little information on
> reproducing the issue, some do have information that might be helpful
> (for audacity team).
> I usually try to encourage the bug reporter to attempt to reproduce, but
> that isn't often successful.
> Anyway, is it useful for these Fedora bug reports to:
> - be announced here on the devel list, or ?
> - added to audacity bugzilla (whether or not the initial reporter is
> responsive ?) ?
> Usually they have a debug trace, with symbols, which I expect would be
> helpful to Audacity-team developers.
My 2p would be that adding useful issues to the Audacity Bugzilla would be
best and would help ensure they get tracked. You would have to have a
Bugzilla account created for you to do that, so if you would like one, please
drop me a line off list.
The current Bugzilla practice is not to list issues that can't be reproduced
until they have at least several reports in the current Beta or SVN, and for
the person reporting to have ascertained if the issue is reproducible in
SVN HEAD or not. If it's only practicable for you to replicate issues in the
latest Fedora package, that would still be useful information. If it isn't
practicable for you to replicate yourself, then perhaps use your own
judgement based on the content you have. For example, might it likely
be a problem with the user's sound device, is it a crash or a cosmetic
issue, and are several other users confirming the same thing?
One definite problem we do have with Linux reports is that a lot of them
relate to older versions of Audacity, so being able to test them in SVN or
the latest package would be regarded as important.