Re: OT: RadarWeb (bugreporter.apple.com)
Re: OT: RadarWeb (bugreporter.apple.com)
- Subject: Re: OT: RadarWeb (bugreporter.apple.com)
- From: Chris Meyer <email@hidden>
- Date: Wed, 5 Mar 2003 15:53:53 -0800
I know your question is off topic but I'll respond anyway since I too
consider it an important question and don't think Apple spends enough
time addressing the issue.
About a year ago I filed the following bug report which is still open.
I'm much more endeared to Cocoa now than I was then and I have to say
that overall Cocoa is an incredibly bug free and fast productive
development environment. And many bugs that I've reported have been
fixed in releases after I've reported them. From my experience Apple
looks at and evaluates each and every bug that is reported and this is
a good thing. My main issue is the feedback (like you) and the ability
to search for existing bugs...
But just for amusement:
Problem ID: 2889996
RadarWeb: No way to search for known bugs
State: Analyze
28-Mar-2002 12:35 PM Chris Meyer:
* TITLE/SUMMARY
I frequently encounter bugs in Cocoa and other Apple software.
Sometimes I put in significant effort to isolate these bugs only to
find out they're a duplicate of something else (see my bug#2885106).
This is a waste of time and is quickly convincing me to switch away
from Cocoa as a development platform. I need compelling reasons to USE
Cocoa but it seems Apple is going the other direction (taking away
cross-platform functionality, not providing source code to Cocoa, and
hiding bugs so that multiple people waste time finding them). Very
unproductive in an otherwise awesome development environment.
* STEPS TO REPRODUCE
1) Read documentation.
2) Try to use something that has a bug in it.
3) Isolate bug to Apple's code.
3) Try to search mailing lists using 1985 search technology. Fail.
4) Try to look elsewhere on web for listing of problems. Fail.
5) Spend more time isolating bug to determine it's really Apple's bug.
6) Report bug.
7) Wait several days.
8) Read about how this is a duplicate of another bug.
9) Wonder why you wasted all this time.
10) Wonder why you're developing in Cocoa in the first place.
* REGRESSION
- Tried to look at bug information in bug reporter (couldn't find any
comments except for my own).
- Searched through my own bug reports for the new bug just in case I
couldn't remember my own bugs. Unsuccessful.
On Wednesday, March 5, 2003, at 02:30 PM, Dan Bernstein wrote:
Hi,
Every once in a while, I follow the popular advice on this mailing
list and "submit a bug report to Apple", using RadarWeb.
It is very frustrating afterwards that I can tell very little about
what's happening to my reports. There are even less columns visible
now in the "my reported problems" table now than when I began
reporting bugs. Yesterday I've noticed a new option, to receive email
notification of updates to bugs you've reported and I've turned it on.
Since then, I've received 3 such notifications, but in 2 out of the 3
cases, there was no change to the information I could see in the
table. It's comforting to know "somebody did something", but still it
would be nice to know what's going on.
Is there a way to have more access to your own originated problems on
Radar? Upgrading one's ADC membership (I'm currently an online (free)
ADC member and a monthly mailing ($200/yr.) subscriber)? Signing an
NDA?
-- Dan
_______________________________________________
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.
_______________________________________________
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.