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: Scott Anguish <email@hidden>
- Date: Tue, 22 Jul 2003 23:51:50 -0400
On Tuesday, July 22, 2003, at 9:43 PM, Wade Tregaskis wrote:
Hopefully someone at Apple pays attention to this. (FWIW, some
information I had to get from a 1997 archive of the Foundation docs,
found via Google!).
Don't hope. File a request through Bug Reporter
<http://bugreport.apple.com/>. It is the only way to ensure that
someone at Apple pays attention.
I won't explain on-list why I don't use the bug reporter, as it'll
probably just start an argument [or worse]. Let's just take it as
given.
Bugs don't get fixed if we don't know about them... and the number of
reports does help prioritize. I'm not sure I see the problem with
writing the report here, and then copying and pasting it into
bugreporter... if you have complaints about bug reporter, well... (and
I realize this is ironic) file a bug... :-)
With that in mind, why is it that Apple can't employee one or two
people to watch the lists, and automatically submit bug reports and/or
documentation updates?
It does happen, but not in any official capacity in many cases. I
watch for any documentation bugs that are mentioned on the list, and
file the bugs.
It seems to be a waste of good money for a $100AU-an-hour developer to
spend that hour reporting a bug, when some evangelistic student could
do it for them at $20AU-an-hour (and who'd be reading the lists
anyway).
reading the lists alone isn't the same as getting first hand
information from the developer. It's unlikely that a reader alone can
get sufficient information in many cases. Plus, that prohibits Apple
contacting the developer for more information, verifying that it's been
fixed, suggesting a work around, etc.
This is a serious question, not a whinge*. I would expect it would
help out everyone - 3rd party and Apple developers alike - if someone
else could worry about the details and producing simple sample cases
and all that.
the sample cases could be specific to your situation. they can't
'know the details' of that.
_______________________________________________
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.