Re: IOEthernetController and USB problem
Re: IOEthernetController and USB problem
- Subject: Re: IOEthernetController and USB problem
- From: Quinn <email@hidden>
- Date: Mon, 11 Mar 2002 10:49:29 +0000
At 10:29 -0500 7/3/02, email@hidden wrote:
Quinn, is there any way that you (or someone), with little effort, could
post (weekly or monthly) the issues that come up in OS X with regards to
networking.
Not easily. When a problem crops up repeatedly we try to write a
developer Q&A that covers it. However, I never feel really happy
about creating a Q&A where, as is the case here, the question doesn't
have a good answer.
<
http://developer.apple.com/qa/index.html>
Also, is there a URL where we can go get the full details on
an issue from the Radar ID #?
AFAIK there are only two ways into Radar for the general public.
o Bug Reporter <
http://bugreport.apple.com/>, but this only lets
you see info about bugs you filed (when it works at all).
o Open Source Bugs <
http://www.opensource.apple.com/projects/bugs.html>,
but this only lets you see bugs that are specially marked as open source.
This bug does not fall under either of these categories, so alas the
details are hidden from you. The main reason I include Radar numbers
in public documents is so that, 2 years from now, if someone really
wants to know how this problem was resolved they can send the Radar
number to us and get the status. The bug numbers also show up in
system release technotes.
The upshot of this is that Radar numbers are not a great way for
non-Apple folks to track the day-to-day status of a problem.
* * *
The opaqueness of Radar has been a major complaint of developers ever
since I've been at Apple. We've made progress in this area (we now
publish Radar IDs, and there are limited ways for non-Apple folks to
get info out of Radar), but we're still a long way from laying Radar
wide open. The primary issue is corporate secrecy. Radar is not
just about bugs; it also contains information about the features,
schedules, and priorities for both software and hardware products.
*Lots* of confidential information makes it into Radar, and there's
no automatic way to filter it out.
Even seemingly innocuous comments can be problematic. For example, a
comment like...
Raising this to a priority 1 bug because it has to be fixed in
PU2 in order to support P57B
... tells you a lot, if you know two easy-to-guess facts:
o PU2 is Mac OS X 10.1.2 (Puma Update 2)
o P57 was the original 'quicksilver' G4's
Thus, one simple comment let's you tie the release date of 10.1.2
(not hard to guess based on our seed programme) with the release date
of our 1 GHz G4's (very very confidential).
Oh yes, and then there's all the bitching, finger pointing, and
recriminations that go into Radar (-:
In summary, wide open access to Radar isn't available and is unlikely
to become available any time soon. However, Worldwide Developer
Relations is interested in entertaining ideas about how to improve
this. The best forum for those ideas is the various feedback
sessions at WWDC.
S+E
--
Quinn "The Eskimo!" <
http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.