On May 29, 2008, at 5:01 PM, Jens Alfke wrote:
On 29 May '08, at 7:48 AM, Sean McBride wrote:
If it was a show-stopper you filed a bug right? All you need to do
therefore is email [EMAIL PROTECTED] and ask if bug #x is fixed in
10.5.3. Presto.
In theory that will work. In practice, it's a waste of time for
everyone to file duplicate bug reports of problems (like this one)
that are already well-known and have been acknowledged many times on
this list by developers and Apple engineers.
The underlying problem is that there's no way for a 3rd party
developer to find the Radar bug number of a problem without filing
their own duplicate of it and waiting for it to come back marked as
a dup.
I can also imagine some scalability problems with Apple developer
support having to manually answer every developer email asking about
a bug-fix...
—Jens_______________________________________________
Jens,
My experience that goes back to the NeXT days tells me that it is not
waste of time to file a bug report, even if you are absolutely sure it
will be marked as a duplicate. First it will help Apple engineers to
prioritize. And second, you can follow when the bug is fixed.
My rule is simple - if I find a bug that bytes me (or incorrect
documentation) I am reporting it as if I was the first person in the
Universe to discover it.
cheers
Georg Tuparev
Tuparev Technologies
Klipper 13
1186 VR Amstelveen
The Netherlands
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
