Bug reporting proceedure, was Re: Bug#24066: libc6: rsh segfaults as , a result of new libc 2.0.7r2
Before I start whining ;-) I want to thank Steve for the useful
information in his bug report, and although his bug report is a duplicate
report, and that is what I am here to complain about, I appreciate his
report and am not directing this at him specifically.
I have never experienced this probem with bug reports until I took on the
glibc package. The willingness of folks to report bugs against this
package is admirable, but without some prudence it creates many, many,
many... duplicates of every problem, sometimes with wildly different
subject lines.
What I am requesting is that the submitter of a bug take some time, in
exchange for the time they expect from the maintainer, and verify that the
bug has not been reported already. If it has, it is appropriate to send
the maintainer a confirmation that you also experienced the bug and any
additional information you can contribute to the solution. This
confirmation should be CC'd to the original bug report, for continuity
purposes. But creating an additional report is both confusing and
administrativly ugly.
I am not looking to stifle information flow about bugs. I am suggesting
that if the reporter of the bug will spend some time "doing the filing"
correctly the task becomes possible and the end user and the maintainer
both benefit.
Waiting is,
Dwarf
--
_-_-_-_-_- Author of "The Debian Linux User's Guide" _-_-_-_-_-_-
aka Dale Scheetz Phone: 1 (850) 656-9769
Flexible Software 11000 McCrackin Road
e-mail: dwarf@polaris.net Tallahassee, FL 32308
_-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_-
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: