On Jul 11, 2005, at 9:22 AM, Elliott Hughes wrote:
longer and more indirect? that would be impressive: being worse than
the usual long and indirect path!
Yes, longer and more indirect. Crashreporter reports are collected,
sorted, filtered and sent to the engineer as "statistical" reports once
they reach a certain threshold. Because they are treated statistically,
it is difficult for engineers to communicate with end users/developers
about the bug (such as "try this workaround" or "can you explain this
bit" or " I can't reproduce, can you tell us more about your setup").
as far as one can tell from outside Apple, all bugs just get thrown
into a black hole anyway. that doesn't exactly motivate me to care
about which submission method to use. submitting a bug report seems to
mean that i'll hear nothing for 18 months, at which point something
may or may not happen which may or may not make a positive difference.
which is probably true even if i don't submit a bug.
I'm sorry to hear that that's been your experience. I can say without
hesitation that I've been fixing bugs literally as fast as I can; but I
can only fix the bugs that are submitted.
maybe the bugs i submitted that got fixed were also submitted by a guy
whose name began with 'X', and that was what it took. how would i
know?
Bugs are fixed according to their importance (mitigated by risk,
obviously). I understand that it's frustrating that your specific bugs
weren't fixed during a particular release (or at all), but it's likely
that there were more important bugs to fix in the timeframe given.
Karl
--
There are few problems in life that couldn't be eased by the proper
application of high explosives.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
