On Thu, Jun 13, 2002 at 04:46:44PM +0100, Keith Whitwell wrote: > It's not that I'm being lazy when I say I don't want to use it. > > First of all, if someone has a bug they want me to fix, they should stick > around long enough to have an email conversation about it. I'm doing free > work for them, if I decide/am able to fix the bug, after all. > > The bug tracker gets in the way of any communication between me & the guy > with the bug. It adds useless work in terms of logging into sf, fighting > with their dumb web frontend, and whatever, every time I want to talk to > the other person. > > Then, worst of all, once I fix the bug I have to go in and tell the damn > thing that it's fixed. Why bother? The other guy presumably already > knows, having been involved throughout...
Interactivity is one of the major problems. The hassle of logging into SF and talking with someone via that mechanism is agreeably terrible. I'm not doubting you on that at all. But you can't force the bug reporter to be on dri-devel. In this case I see the SF bug system as a mechanism for first call. Then hopefully - they leave their email address (that doesn't always happen), and you can begin the interactivity session. Once fixed, they already know it's fixed, so just 5 minutes to close the bug. That way it stops someone else picking it up and trying to work on something that's already been fixed. We certainly don't have to use it for logging every single thing we do on rectifying the bug. It's just a means of identifying the person resposible for fixing it, so others can poke at the developer too. Does anyone know whether we can enforce someone to leave their email address on the SF bug database ? Alan. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
