On Friday 07 March 2003 11:20 am, Buchan Milne wrote: > Bret Baptist wrote: >> The moving from UNCONFIRMED to NEW is what I would like to do. One of the >> issues I have is that I test a component for bugs (say kdebase). I can >> only vote for one bug out of that component. So that means that I can only >> really confirm one bug in the system. I can post "Me too's" to a comment >> on a bug, but I can not vote for multiple bugs and move them to a NEW or >> CONFIRMED state in the system. Does this make any sense? >> > Not as much as it could. Saying "me too", or voting/confirming a bug are > not really useful unless you can add more insight to it. Better to > ensure that when the developer looks at it, that he has something to > work with, than to make him look at a whole bunch of bug reports that > have information on how to reproduce the bug. > > MHO of course. > > Buchan
I thought the idea was that if a bug gets voted to a confirmed state than the developer would have a pretty good idea that the bug is in fact valid. I was also under the impression that if the bug is not in a NEW state that most developers (pixel, and fcrozat being an exception for sure) don't even look at it. Is this not the case? -- Bret Baptist Systems and Technical Support Specialist [EMAIL PROTECTED] Internet Exposure, Inc. http://www.iexposure.com (612)676-1946 x17 Web Development-Web Marketing-ISP Services ------------------------------------------ Today is the tomorrow you worried about yesterday.
