Re: Bug reports and documentation updates (was Re: Subclassing NSPort (or NSSocketPort))
Re: Bug reports and documentation updates (was Re: Subclassing NSPort (or NSSocketPort))
- Subject: Re: Bug reports and documentation updates (was Re: Subclassing NSPort (or NSSocketPort))
- From: "M. Uli Kusterer" <email@hidden>
- Date: Wed, 23 Jul 2003 06:07:18 +0200
At 23:05 Uhr -0400 22.07.2003, publiclook wrote:
And don't spend more than 10 minutes either because if you spend
hours or days working down to the essence of the bug and provide a
small working application that demonstrates the bug and can explain
to Apple exactly what is wrong, it doesn't do any good! You cant
attach such information to a bug report
You should verify your claims: Once you have filed a bug, there's a
link that lets you send additional files via e-mail that will be
filed along with your bug, like sample apps etc.
and you will never hear from Apple again. They won't reliably tell
you the status of your bug or if they have any intention of
confirming it let alone fixing it. The bug will either get fixed in
a later release leaving you to wonder if your effort helped at all
or it won't get fixed and you will know your effort didn't help.
My mileage varies :-) There could be more feedback, but occasionally
I received requests to confirm whether a particular bug was still
present in the newest release. Actually, they kept pestering me to
test for two bugs in particular in the Jaguar pre-release. Tough luck
if the person you're bothering doesn't have a seed key and thus won't
be able to confirm the bug themselves. Even sending the request four
times doesn't help in that case...
In my experience, submitting bugs to Apple is a waste of valuable
time and an exercise in frustration and futility. Let them find and
fix their own damn bugs if they can't exert themselves enough to
even confirm a bugs existence.
Actually, I think the worst part of it all is how duplicate bugs are
handled. I filed a bug against Radar, requesting that they add
automatic display of the bug number mine is a duplicate of, and of
that bug's state. But no, instead I have to bother DTS to find out
about the state of my bugs, and if I don't keep all those
confirmation mails on file, I have to bother them even more by making
them look up the originals to my duplicates. *that* is what I call
wasted manpower.
But you're right: On the topic of feedback, both the MacOS X GUI and
Apple's bug reporter could use some improvements. There once was a
way to be notified when one of your bugs was changed ... *that* was
useless. You simply got an e-mail "your bug was changed". I never
found our why they didn't bother to tell me *what* the heck changed...
--
Cheers,
M. Uli Kusterer
------------------------------------------------------------
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
_______________________________________________
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.