• 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 reports and documentation updates
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug reports and documentation updates


  • Subject: Re: Bug reports and documentation updates
  • From: "Alastair J.Houghton" <email@hidden>
  • Date: Wed, 23 Jul 2003 16:24:11 +0100

On Wednesday, July 23, 2003, at 03:24 pm, Phill Kelley wrote:

I don't think it's good enough for Apple to say that they judge how
important a bug is by the number of people who report it.

Trouble is that that is a very good measure of how annoying the bug is, which is the primary concern when trying to prioritise bugs. It doesn't really matter about a kernel panic that happens once every ten million years if you've got a UI redraw glitch that really winds your users up.

By the way, I think you have misconstrued what Scott said on this subject... he actually said that the number of people reporting a particular bug "does *help* prioritize", which is a world away from your complaint that they're judging importance based on the number of duplicates.

Duplicate reports aren't always a waste of time, either. Sometimes when tracking down/fixing a bug, all of the duplicate reports can be very illuminating.

There *is* an alternative. Simply make the Radar database searchable. That
way, when you or I notice a problem, we can go and see if it has already
been reported.

You need to file a bug report saying this. This mailing list, whilst it gets read by some Apple employees, isn't an official mechanism for contacting Apple and unless one of their people sees your mail and raises the issue themselves, you won't get anywhere.

I agree that it'd be nice if we could search Radar ourselves, although I can see reasons why Apple might not want to provide everyone will access to all of the information it holds. Perhaps being able to search customer-reported bugs would be enough.

Kind regards,

Alastair.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Bug reports and documentation updates (From: Phill Kelley <email@hidden>)

  • Prev by Date: How to get a list of all classes known to the runtime
  • Next by Date: [OT] Re: Bug reports and documentation updates (was Re: Subclassing NSPort (or NSSocketPort))
  • Previous by thread: Re: Bug reports and documentation updates
  • Next by thread: Re: Bug reports and documentation updates
  • Index(es):
    • Date
    • Thread