[OT] Re: Bug reports and documentation updates (was Re: Subclassing NSPort (or NSSocketPort))
[OT] Re: Bug reports and documentation updates (was Re: Subclassing NSPort (or NSSocketPort))
- Subject: [OT] Re: Bug reports and documentation updates (was Re: Subclassing NSPort (or NSSocketPort))
- From: Shawn Erickson <email@hidden>
- Date: Wed, 23 Jul 2003 08:19:23 -0700
On Tuesday, July 22, 2003, at 08:05 PM, publiclook wrote:
On Tuesday, July 22, 2003, at 09:53 PM, cricket wrote:
You may be the best person to verify a bug once it's fixed (because
you might be the only person that's seen it _and_ reported it).
That's why it's especially important for you to file a bug if you see
one. Also, filing bugs is not a one-way communication. Often
additional information is needed before the bug can be truly
understood and fixed, and being able to contact the person that
originally saw the bug is invaluable.
It shouldn't take more than a 5-10 minutes to file a good bug.
Exactly!
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 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.
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. If you desperately need a fix and can show
Apple exactly what is wrong in a concise way, the incredible wall of
silence that results is even more frustrating. Just don't waste your
time.
BS
I have submitted several bugs to Apple and have heard back on many of
them and most have been fixed. I usually get email letting me know that
the fix is expected in the XX prerelease could you please download it
and verify that what I reported was fixed, etc. On a few of them I let
them know that it wasn't fully fixed and they revved the fix, I even
emailed back asking for the source (darwin related issue in this case)
because I couldn't quickly down the prerelease.
Remember folks Apple has a large mass of products and a database with a
large amount of reported bugs and enhancement request... items do have
to get prioritized (all bug are not equal, what may be important to you
is not that important in the see of currently filed defects).
If you don't take the time it is likely your problem with not be
addressed. If you do take the time you are helping to get your problem
resolved. In addition to bug reports consider using a DTS incident if
the fix is critical to your product.
If you feel things are going as well as you want PLEASE talk with the
DTS folks at Apple to let them know you are unhappy... complaining on a
public list isn't going to help much.
-Shawn
_______________________________________________
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.