RE: Revisiting NSTextView bugs in Interface Builder (rant about B ugRe porter)
RE: Revisiting NSTextView bugs in Interface Builder (rant about B ugRe porter)
- Subject: RE: Revisiting NSTextView bugs in Interface Builder (rant about B ugRe porter)
- From: Jeff Laing <email@hidden>
- Date: Tue, 11 Jan 2005 13:26:03 +1100
> From: John Stiles [mailto:email@hidden]
>
> It's a bug, and they know about it already.
> They'll ask you to verify it when they seed a fixed IB.
> Chill out, they get hundreds of bugs a day :)
I don't see how you can know this, from *my* experience. Certainly I assume
you've used it more than I have.
Since the website only lists Open/Analyze and Open/Verify, I guessed that
the states were something like
Open/Analyze - an engineer is looking at it
Open/Verify - an engineer has confirmed it is a defect
...
Closed/Duplicate - someone else already reported something like this so we
won't track it twice
I don't know why you are confident in saying that "its a bug and they know
about it already", and assume this implies that they've reproduced it, or
have fixed it. Yes, its a duplicate, but what tells me the original defect
is not still sitting Open/Analyze or even New/BeingIgnored ?
(especially given that when I posted the problem to this list, no-one seemed
to be able to reproduce it)
In *our* defect tracking system (ClearDDTS), we distinguish between
"Resolved/Not a Bug" and "Resolved/Fixed Next Rev" (and a bunch of other
variants - when something is tagged as a duplicate, you get to see what the
status of the original defect is).
Again, this rant is about *my* experience - other people may well have
gotten more information. But to my eye, its a pretty low-content response
that certainly does not encourage me to submit future bug reports - the
outcome here has been "well, I have to work around it as best I can, because
I can't wait for the next rev of IB in which the problem *may* be fixed.
Because I'll work around it (I'll never use subclasses of NSTextView in my
nibs), this bug will never bite me again. Therefore I don't really care if
it gets fixed or not. Next time something like that happens, I may as well
ignore bugreporter since it makes no discernable difference to me".
Fairly crappy attitude, I agree, and in fact its *not* the one I have. But
I could understand the developer who *did* come away with that lack of
respect for bugreporter.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden