Re: Bug reporting proceedure, was Re: Bug#24066: libc6: rsh segfaults as , a result of new libc 2.0.7r2
On Thu, 16 Jul 1998 Marcus.Brinkmann@ruhr-uni-bochum.de wrote:
> On Wed, Jul 15, 1998 at 09:49:33PM -0500, John Goerzen wrote:
> > Dale Scheetz <dwarf@polaris.net> writes:
> >
> > > > NO! Let's not annoy bug submitters!
> > >
> > > But annoying developers is just fine ;-)
> >
> > Yes. Because the usual reason for something to not be closed is that
> > the developer either forgot to close it or hasn't done anything about
> > it yet.
>
> I agree with John here. Dale, for small to medium packages, duplicated
> bug reports are not a problem at all (indeed I´m happy if something
> is brave enough to report a bug). If I know about bugs in my packages which
> never are reported -- is nobodyone using my package or what?
I agree with John as well, for small and medium packages, maybe even for
all packages except glibc.
This may very well only be a problem for the glibc packages. As no one
else has said "Yes, I'm having the same problem!", I suspect I am alone
with this problem.
This probably means that a "general" policy of any sort will do me little
good.
>
> However, there are some packages were the number of bugs reported and
> open is terrible, and it requires a lot of work to clean this up.
>
> I was surprised about your complaint. The last time, you just asked
> for some people to help you with the bug reports. I remember that
> I thought this was the right reaction. Has this changed? Some people
> have offered you their help. Why didn´t you asked again?
>
I guess I just prefer to whine ;-)
The help I got was greatly appreciated, but very short lived. I think one
pass was made, several bugs closed, and the crew went home. This was
during the time of my disasterous disk crash, so I lost their addresses,
and they never got back with me...
I guess I was looking for a solution that spread the load around more
evenly.
> FWIW, i you need help with the bug reports, I can take a look at
> them. Just let me know.
>
Any help in this reguard would be greatly appreciated. The two primary
tasks that I would ask for include weeding out archaic bug reports that
are no longer of value and verifying that supposedly fixed bugs realy are
fixed in the reporters environment. Some help prioritzing the remainder
would be helpful, but not necessary.
I suspect that the real solution must come from a policy statement about
group maintainership or team maintainance of packages, and tasks.
Thanks,
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: