• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Bug in Xcode 2.2
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug in Xcode 2.2


  • Subject: Re: Bug in Xcode 2.2
  • From: Robert Dell <email@hidden>
  • Date: Mon, 14 Nov 2005 05:13:17 -0500

Piers Uso Walter wrote:


Am 13. Nov 2005 um 16:28 schrieb Adriaan van Os:

No, I gave up doing that, it is just as naive as throwing money into a wishing well - in the last twenty years I never even got a reasonable reply from Apple.


I understand where you're coming from, but you might want to reconsider.

Reporting bugs via radar is not about getting replies from Apple, but rather about increasing the likelihood of your bugs getting fixed. It has been often stated by Apple employees on this list and elsewhere that the number of bug reports concerning specific issues plays an important role in prioritizing these issues internally at Apple.

Over the years, I've reported many bugs/feature requests, and am happy to report that, sooner or later, more than two thirds of those have been fixed. Since some of my reports dealt with rather arcane issues, I have reason to believe that my reporting was instrumental in getting them fixed eventually.

Of course, sometimes I had to wait for one or two major revisions (e.g. many bugs I reported for 10.2 were not fixed before 10.4, similarly with Xcode 1.2/2.2), so using radar is definitely not something for the impatient.

But comparing it to a wishing well seems too harsh. (or maybe not - I guess this depends on how strongly you believe in the effectiveness of wishing wells ;-)

Actually, my experience lately on apple's bugreporter page when ATTEMPTING to report my xcode 2.2 editor bug earlier encountered an error 500 from apple's server. This means the bug wasn't submitted. I tried 3 times and got the same error 500. So, my latest experience of bugreporter.apple.com leads me to believe it's not only a wishing well but a wishing well with a rubber cap on it to prevent pennies from getting into it.


_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Bug in Xcode 2.2 (From: Adriaan van Os <email@hidden>)
 >Re: Bug in Xcode 2.2 (From: Adriaan van Os <email@hidden>)
 >Re: Bug in Xcode 2.2 (From: Piers Uso Walter <email@hidden>)

  • Prev by Date: [Xcode 2.2] How to fix "Multiple build commands for output file" warning ?
  • Next by Date: Re: [Xcode 2.2] How to fix "Multiple build commands for output file" warning ?
  • Previous by thread: Re: Bug in Xcode 2.2
  • Next by thread: Re: Bug in Xcode 2.2
  • Index(es):
    • Date
    • Thread