On 5/29/08 8:01 AM, Jens Alfke said: >> 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...
Maybe if they start to suffer from those 'scalability problems' they'll address the root causes (that you outlined nicely). :) -- ____________________________________________________________ Sean McBride, B. Eng [EMAIL PROTECTED] Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ 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]
