500+ developers so far have submitted this to Apple.
Fix Radar or GTFO
21–30 of 36 posts
Re: Fix Radar or GTFO
#22I never got any feedback on this bug at all (just like always).
But, this Apple guy looked up the bug on their internal radar tool (a native Mac app, not some crappy web interface). There were screens full of discussion, with engineer's names I recognized, and the bug has been elevated to "Show-Stopper" status, which he told me meant the next release wouldn't ship without a fix.
What I took from this is that Apple's internal tools for bug triage, discussion, and prioritization are relatively sophisticated and heavily used, but they have nothing to do with the pathetic, rude, uninformative Radar interface that we peons who pay Apple for the privilege of developing for their platform get to see. It was kind of interesting to get a peek inside from their perspective.
Having said that, though, I almost never file Radar issues anymore, for exactly the same reason that I don't go to Apple's offices and clean their toilets for free.
Re: Fix Radar or GTFO
#23This has been solved already: http://openradar.appspot.com If you file a new bug with Apple, publish it here as well. No more black hole, you can see what others have already posted. You can even see what duplicates are about (if the original bug was also at open radar).
Re: Fix Radar or GTFO
#24"Fix Radar or... Carry on making large sums of money regardless." Developers aren't their primary concern. Look at Xcode for crying out loud (and wonder at its magical ever-crashing nature).
XCode has never crashed for me in 3+ years. Your project is corrupt. You're doing something wrong. Look to a professional for assistance with your IDE.
Re: Fix Radar or GTFO
#25Re: Fix Radar or GTFO
#26Did anyone else click on the link hoping for a nice juicy technical article about RADAR ( http://en.wikipedia.org/wiki/Radar ) and not some whining about a piece of software that would have been fixed by now if it was open source?
Re: Fix Radar or GTFO
#271. For security issues, use full disclosure. I received phone calls immediately when I included something like "disclosure in 30 days unless otherwise requested". Otherwise bugs were fixed in the next OS release a year later.
2. Otherwise: our Apple rep (.edu) told us that bugs were prioritized based on how many Macs you couldn't buy until it was fixed. Later, this changed to how the bug was preventing you from deploying iPhones (“iPhone: it's like sudo for Apple”) and I imagine this now includes iPads.
Re: Fix Radar or GTFO
#28If you file a bug report on Radar, unless you know someone at Apple who you can give the Report ID to, it is unlikely to be dealt with quickly. Seems like they don't have a dedicated team overlooking it.
Re: Fix Radar or GTFO
#29There's already an effort to do this: http://fixradarorgtfo.com/ 500+ developers so far have submitted this to Apple.
Re: Fix Radar or GTFO
#30I've filed many bugs with Apple over the years. There are two strategies which work: 1. For security issues, use full disclosure. I received phone calls immediately when I included something like "disclosure in 30 days unless otherwise requested". Otherwise bugs were fixed in the next OS release a year later. 2. Otherwise: our Apple rep (.edu) told us that bugs were prioritized based on how many Macs you couldn't buy…
I love this so much. "Unless otherwise requested". Perfect.