Bug tracker suggestion.
Bug tracker suggestion.
- Subject: Bug tracker suggestion.
- From: Benjohn <email@hidden>
- Date: Thu, 17 Feb 2005 18:41:44 +0000
I was reviewing my bugs on Apple's bug tracker yesterday. I noticed
that all of my closed bug reports are replicates of existing bugs.
It's obvious that if Apple's bug reporter could be publicly searched:
* I would have saved a lot of time that I spent hunting down a bug
that turned out to be caused by a known Apple framework bug (about a
week in the case of a recent example).
* I would have saved the time that I spent filing in a bug report
(which in the cases where I build a reproduction case could be several
hours).
* I would be more likely to tick on an already known bug and vote it
up a notch. It's much easier to work around a problem (which you're
going to have to do anyway) than to find out the exact cause and report
it.
I've had a Google around, and this topic has, unsurprisingly, been
discussed before. Could someone point me at the overwhelmingly good
reasons why the database isn't public and searchable (or mostly public
and searchable - I understand there may be individual disclosure
issues)? It seems that with the current system, we're all wasting a lot
of time on a frustrating endeavour, when it ought to be spent on
writing great software.
If there isn't an overwhelmingly good reason for the current system,
the obvious solution is to stop using Apple's bug tracker, and use a
public one instead. That way it's searchable by all of us, and remains
equally useful for Apple too. While we're there, how about a rich app
too (integrating known reports in to the xcode documentation), rather
than sucky web forms :)
Cheers,
Benjohn
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden