Re: Build Results window feature request
Re: Build Results window feature request
- Subject: Re: Build Results window feature request
- From: Laurence Harris <email@hidden>
- Date: Fri, 22 Jun 2007 20:04:34 -0400
On Jun 22, 2007, at 6:33 PM, Martin Redington wrote:
If you're doing it for fun then anything's possible (but smaller
projects like this are more likely ;-). There is a gotcha here,
though. Any bug reporter application would have to integrate with
Apple's Radar system, so no one can just go off and write such a
beast on his own.
Not necessarily.
If the bug reporter app fed into its own public "community"
database., then that would allow Apple engineers to look at what's
being reported out in the community (and they could be annotated
with corresponding radar reports,
I doubt Apple has anyone who's going to devote much time to pouring
over bug reports in a public database not maintained by Apple.
or even just promote bugs to radar semi-automatically when
appropriate)
This is probably not going to be very useful. A lot of developers
don't want to report bugs in a public system. They need a system that
allows them to report them to Apple in a way that keeps all of the
information they supply confidential. Apple wants to be able to
contact the person who reported the bug, in case they need additional
information and so they can ask the original filer to confirm the
bug's been fixed. Radar gives them all this.
, but, more importantly, would allow the community to swap
information and workarounds in a way that simply isn't possible
with the (almost) black hole that is (for understandable reasons)
Radar.
A public database would not be a substitute for Radar, nor would it
serve the same purpose. It might help smaller developers work around
bugs, but it wouldn't serve as a reporting mechanism for Apple and
hence wouldn't put bugs in a queue to be considered for fixing. An
application for such a system would not be at all what I'm
discussing, nor would I have any interest in something like that. I'm
marginally willing to report problems in the hope I can help get them
fixed, but the system you describe wouldn't do that. I'd have to
report them both places and one is already too many sometimes. ;-)
be much of a commercial proposition. The overhead (in time and
effort) for bug reporting is already too high, and most of that
overhead is in identifying a good test case and writing up the bug
itself. Filling in the OS version etc. is insignificant in
comparison, at least for me.
Most of the bugs I end up reporting are pretty easy to reproduce.
100% reproducible for me in many cases. It still takes more time to
describe most problems than do the tedious stuff, but eliminating the
tedious stuff would still be worthwhile IMO. Years ago when I started
doing shareware, I only accepted payments by check. When I changed
that to allow people to use a credit card on the web my revenues
jumped up considerably. Does writing a check and addressing an
envelope require a major effort? No, but you'd think it was to listen
to them whine about it, and it's enough to discourage a lot of people
from doing it.
Larry
_______________________________________________
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