Re: Reporting bugs... (Was-- Re: Xcode bug)
Re: Reporting bugs... (Was-- Re: Xcode bug)
- Subject: Re: Reporting bugs... (Was-- Re: Xcode bug)
- From: Henry McGilton <email@hidden>
- Date: Tue, 28 Oct 2003 12:56:57 -0800
On Tuesday, October 28, 2003, at 10:31 AM, b.bum wrote:
Rest assured that Apple does not ignore bug reports.
I am sure that Apple do not ignore bug reports. However, the
minimal level of feedback gives one the perception that the bugs
are just being filed away.
It helps if your bugs are clearly written, have steps to reproduce (if
possible), and a screenshot. Even if you can't reproduce the bug, if
you can provide a screenshot and/or a crash log, that information will
be tracked.
I have submitted three bugs this year. Two of them were bugs in Safari.
One problem is in the window server itself.
One of the Safari bugs was fixed in Safari 1.0 --- thank you Safari
team, as
it was a real show-stopper.
But the feedback I got on it after it was fixed was less than
encouraging. Instead
of saying 'we fixed that bug with Version 1.0', the feedback stated 'we
can't
reproduce the bug in Version 1.0'.
The second Safari bug has not been fixed. I consider the second bug to
be serious,
but there has been no feedback as to whether the Safari team considers
it a bug,
and what they will do to fix it, and especially, if it will ever be
fixed.
I have had to code in some kludgey workaround code to get around this
bug and
the situation is highly unsatisfactory all around. And it's the
uncertainty
that is most frustrating.
It would help greatly if the Safari web page on the Mac OS X web site
would
state what the current version is.
In the case of the window server problem, I did receive feedback, but
the feedback was so ambiguous and self-contradictory that I can not
tell readily
if Apple have decided it's a bug or a feature, and whether or not it
will ever
be fixed. So I have had to go off and write workaround code, based on a
vague assumption that the bug will never be fixed, and then if it ever
*does*
get fixed, I'll be stuck with ripping out the workaround code and
informing
all of my customers.
I am not sure what the solution is to the problems created by
keeping the bug database private. What I am sure of is that the
situation is frustrating a lot of developers. Speaking for myself,
I would much rather contribute to improving the overall product,
because that would be a winner for the developer community as well
as Apple. But we can't very well contribute anything when we don't
know what's going on . . .
Apple need to raise their consciousness to the fact that bugs in
Mac OS X can manifest themselves as bugs in developer products, and
when they do, it's the developer who gets the E-Mail from customers.
Maybe if I relayed my customer's bug reports straight to Apple support,
there might be a better appreciation of the problem.
Best Wishes,
........ Henry
===============================+============================
Henry McGilton, Boulevardier | Trilithon Software
Objective-C/Java Composer | Seroia Research
-------------------------------+----------------------------
mailto:email@hidden |
http://www.trilithon.com
|
===============================+============================
_______________________________________________
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.