Re: Bug reporting proceedure, was Re: Bug#24066: libc6: rsh segfaults as , a result of new libc 2.0.7r2
Geeze, the crossposting is horrendous. I don't see this as a policy
issue, so followups to debian-devel or debian-user only please.
Dale Scheetz <dwarf@polaris.net> writes:
> On 29 Jun 1998, Manoj Srivastava wrote:
> > Make bug reporting any more onerous than it is, and peole
> > merely stop filing reports.
> What is so "onerous" about checking to see if the bug has already been
> reported? As Rob said, it could provide the "work around" information that
> is needed to resolve the problem.
>
> Suggesting, even strongly, that it is proper proceedure when submitting a
> bug, to research the bug reporting system first, and provide useful
> information second, doesn't seem onerous to me, and has several practical
> uses for the bug submitter, as well as the maintainer.
I agree with Dale. I think we should encourage submitters to check
the BTS before posting. But the reality is, this will not always
happen; I don't think we should flame people for not checking first.
I think it's important to at the same time make it easy for bug
submitters and easy for package maintainers. I don't think we're out
of line asking a bug submitter to check if the bug is already
reported. For instance, if I submit a bug against CVS or bash, they
always say, "read the known problems list first, and/or read the FAQ
first." Checking the BTS is easy in comparison to having to read a
whole big FAQ.
--
.....A. P. Harris...apharris@onShore.com...<URL:http://www.onShore.com/>
--
To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: