Re: Reporting bugs... (Was-- Re: Xcode bug)
Re: Reporting bugs... (Was-- Re: Xcode bug)
- Subject: Re: Reporting bugs... (Was-- Re: Xcode bug)
- From: Nicholas Riley <email@hidden>
- Date: Tue, 28 Oct 2003 16:14:02 -0600
- Mail-followup-to: Henry McGilton <email@hidden>, email@hidden
On Tue, Oct 28, 2003 at 12:56:57PM -0800, Henry McGilton wrote:
>
But the feedback I got on it after it was fixed was less than
>
encouraging. Instead of saying 'we fixed that bug with Version
>
1.0', the feedback stated 'we can't reproduce the bug in Version
>
1.0'.
This is standard procedure. I'd consider it a bit presumptuous to say
"we've fixed your bug" - especially if you retort "no we haven't!"
That they couldn't reproduce your bug may mean what you hope - that
it's fixed - but it also might mean they've only fixed part of your
problem, or they misread or misunderstood your reproduction
instructions, or that your system configuration and that of the person
who tried to reproduce the bug didn't match, or...
If you can still reproduce the bug, then respond to the 'we can't
reproduce' email, explaining why your bug hasn't been fixed, and it
will be reopened. I've done this several times, most recently with a
bug involving NSOpenPanel behavior in which the behavior actually got
worse instead of better.
>
The second Safari bug has not been fixed. I consider the second bug
>
to be serious, but there has been no feedback as to whether the
>
Safari team considers it a bug, and what they will do to fix it, and
>
especially, if it will ever be fixed. I have had to code in some
>
kludgey workaround code to get around this bug and the situation is
>
highly unsatisfactory all around. And it's the uncertainty that is
>
most frustrating.
So email email@hidden and ask about the status of your bug,
explaining its importance.
>
In the case of the window server problem, I did receive feedback,
>
but the feedback was so ambiguous and self-contradictory that I can
>
not tell readily if Apple have decided it's a bug or a feature, and
>
whether or not it will ever be fixed. So I have had to go off and
>
write workaround code, based on a vague assumption that the bug will
>
never be fixed, and then if it ever *does* get fixed, I'll be stuck
>
with ripping out the workaround code and informing all of my
>
customers.
So ask for clarification! I've received multi-paragraph answers from
engineers when I've done so. You seem to think that the channel to
Apple is one-way once a bug is opened. It's not.
--
=Nicholas Riley <email@hidden> | <
http://www.uiuc.edu/ph/www/njriley>
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.