Unfortunately the bug reports have often been... sparse. A mildly descriptive subject (which is fine) and a bug report that reads "See the discussion on perlmonks, at http://...". This, unfortunately, is bad.
When making a bug report, the report itself needs to have enough information in it to reproduce the problem. Someone should, while completely off-line, be able to read the bug report and (hopefully) do something about the bug. Putting a link to extended discussion on the problem in the report is fine, but the report itself should be sufficient to work with.
If that information's not handy, the bug is much less likely to be looked at. Following the link, when it's not even clear (because of insufficient information in the report) that there even is a bug, is enough extra work that far fewer people are likely to look at the bug, and the fewer eyes the lower likelyhood that the bug will be fixed.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: On making bug reports (For both perl and non-perl software)
by mirod (Canon) on Dec 02, 2002 at 19:40 UTC | |
|
Re: On making bug reports (For both perl and non-perl software)
by hossman (Prior) on Dec 03, 2002 at 01:53 UTC | |
|
Re: On making bug reports (For both perl and non-perl software)
by dingus (Friar) on Dec 03, 2002 at 10:28 UTC |