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: David Thorup <email@hidden>
- Date: Wed, 23 Jul 2003 01:59:20 -0600
On Tuesday, July 22, 2003, at 07:53 PM, cricket wrote:
>
It shouldn't take more than a 5-10 minutes to file a good bug.
Oh how I wish that were the case. However, a really "good bug" takes
much more than 5-10 minutes to file. For those really good bugs you've
got to come up with a test case that showcases the bug. It must also be
separate from your application, because let's face it, your manager
wouldn't be too happy if you sent the entire source code of your
company's flagship product to Apple just so they could fix a bug. Many
times the "really good bugs" take place in very complex parts of your
application and it takes a lot of time to create a sample application
that reproduces the bug.
There's been many times when I haven't filed a bug, or have waited a
very long time to file one, simply because I don't have the hours
needed to create an adequate sample application and file a good bug
report. I'm usually busy with other things and can't justify the time
to file a bug with Apple.
_____________________________
Dave Thorup
Software Engineer
email@hidden
http://www.kuwan.net
Defaults Manager - The premier editor for Mac OS X's User Defaults /
Preferences database.
_______________________________________________
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.