Re: [OT] Bug Reporter Questions
Re: [OT] Bug Reporter Questions
- Subject: Re: [OT] Bug Reporter Questions
- From: Scott Anguish <email@hidden>
- Date: Sat, 17 Apr 2004 02:09:48 -0400
On Apr 16, 2004, at 11:23 PM, Allan Odgaard wrote:
Most of this is off topic and just to settle my curiosity, sorry! But
this was the only forum which I could think of, and probably others
may find potential answers interesting :)
I have on two occasions experienced that I wanted to check the status
of a reported bug, only to find that it was simply missing from the
Bug Reporter. Did anyone experience similar? Is the database perhaps
cleaned once in a while (removing closed bugs), or am I just getting
old (remembering reporting bugs that I didn't ;) ).
Nope, I think all the bugs are there from the beginning of time.
Yep. Here's bug #1
rdar:/problem/0000001 Subject: Single Cell Life Form Mutates
Is it possible to view bugs other than those I reported myself? e.g.
sometimes I see bug IDs quoted, but is there a place I can actually
look at the description for that bug? And is it perhaps even possible
to do plain-text searches in the database?
Nope.
Does anyone know how priorities are assigned to bugs? I often see
people asking others to report some missing/wrong functionality, even
though there already is one, but with the argument that: "maybe that
will give it higher priority".
It of course depends on the type of bug. 20 people saying "making
mail to blah causes a kernel panic" is probably as effective as 1
person, since it's a significant problem. Those extra reports make it
easier to track down the problem (especially with crash logs included!)
Doc bugs are very much reliant on duplicates, since it's not
necessarily evident that Joe Developer can't grok the new Foundation
Twitters class because mmalc wrote lousy doc*. And while one person
not being able to understand mmalc's lousy doc might just be that
person, 20 people means that there is a problem.
Is that really so?
I wouldn't lie to you.. :-)
Is the "severity" of the bug perhaps used? Generally I report most as
"Serious Bug / No workaround" even when the bug actually does "Crash
or Data loss", but normally it has the workaround of simply not using
the functionality or similar, so "Data loss" sounds to strong to me.
All bugs are screened, since someone has to decide which group gets
which bugs.
Basically, though the severity you supply is a good indicator of the
seriousness, but overall, if you get a system crash, an app crash (our
app) or suffer data loss, that's the way to go...
Does anyone have any circa figures about how many bugs gets reported?
Cause the bug IDs are clearly ascending, and when reporting several
bugs in a row, the distance between the IDs are <10. But if every bug
ID is raised with only one (and the ID is unaffected by date or
similar) then it would seem they get almost a thousand reports pr.
day, which to me seems quite unmanageable, given that bugs are not
really classified other than "Mac OS X" versus "Developer Tools".
Ah.. not to _you_ they're not classified, but when they get screened
they get sent to the right department, and screened again and
classified.
Also, radar isn't just necessarily bugs. That's what you submit to
it, but it also includes enhancement requests, and I regularly use it
to remind me that my Laundry needs picking up at the dry cleaners.
Is there any explanation of what "Open / Analyze" and "Open / Verify"
means? I.e. does the latter mean that they were actually able to
verify it? Cause from the page it sounds more like they are in the
process of trying to verify it, which would mean that "Open / Analyze"
means they haven't looked at it yet (?), but I have like 30-40 bugs as
"Open / Analyze", hopefully someone has at least read my summary ;)
Open/Analyze doesn't mean that we've not looked at it. Outside folks
don't get to see what happens, who reads what and when, and the
intermediate steps between Analyze and Verify.
Verify means that the submitter is expected to verify that the bug has
been fixed. With outside developers that means sometimes waiting till
the next release.
If you feel that bugreporter doesn't give you the information you
need, by all means contact ADC. I can understand the frustration that
some folks feel, especially when someone here tells them to file a bug
-- and it's a dupe -- and it gets closed almost immediately as a dupe.
Just because that happens doesn't mean that your submission was a waste
of time. Those are all related to the non-duplicate submission, and
are still important and useful.
* turning his crank here folks!! :-)
_______________________________________________
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.