Re: General query
Re: General query
- Subject: Re: General query
- From: Ben Byer <email@hidden>
- Date: Thu, 29 Nov 2007 19:07:33 -0800
On Nov 29, 2007, at 6:28 PM, Peter O'Gorman wrote:
Kevin Van Vechten wrote:
On Nov 29, 2007, at 5:08 PM, Robert A. Weller wrote:
A few days ago I posted an issue here involving Xcode's interaction
with X11 and received an immediate confirmation of the bug from
another list member who had a nice work-around. -Thanks!
We have now accumulated a number of additional Xcode issues
related to
using the new unified console window with command-line applications.
What is the most effective way of providing feedback on these
issues?
http://developer.apple.com/bugreporter/
This is certainly the best way to provide feedback and report bugs,
however there is an Xcode mailing list also:
http://lists.apple.com/mailman/listinfo/xcode-users
Seconded. Put slightly differently:
If you file a bug report at developer.apple.com/bugreporter, you can
be confident that the correct Apple engineer will see the bug, and it
will remain in their queue until they do something about it. This
occasionally fails, as with the Xcode / DISPLAY thing, when you have
a bug that involves interaction between multiple programs (and
multiple groups at Apple). When your bug is received, Developer
Relations has people whose job (as I understand it) is to correctly
pick the software component most appropriate for the bug report, which
then causes the bug to be forwarded to the engineer responsible for
that component.
When you have a lot of bugs coming at you (I'm seeing about 5-15 bugs
per day, personally, and I bless you all for them), there's time
pressure involved there to find a quick way of dealing with bugs.
Usually, that means I'll either A. mark it as a dupe of another bug,
B. realize the bug should go to a different component (for example,
some of the Spaces/X11 interaction bugs will need to be handled by the
Spaces group) and forward it there, C. send it back with an
explanation of why it's not really a bug, or D. send it back with a
request for clarification from the developer. (As I believe Jordan
noted, that's why you must sign up for the free ADC account to file a
bug.)
In this case, choice C happened where it should have been B, and it's
a mistake I've made many times. We are human. :)
On the other hand, posting to one of the Apple mailing lists gives you
an opportunity to find out if other users are seeing the same issue,
and generally the Apple Engineers who work on that software try to
monitor the list and answer questions, and get more information so
that the problem can be better understood. It's more difficult to do
that with bug reports, due to the overhead involved with tracking the
reports.
That's why I generally like to talk about bugs here, openly, but ask
you to file an official report so that it's properly tracked in the
system.
--
Ben Byer
CoreOS / BSD Technology Group, XDarwin maintainer
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden