site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com mh On Oct 22, 2009, at 1:12 PM, Kevin Van Vechten wrote: Hi Matt, On Oct 22, 2009, at 10:58 AM, Matt Haffner wrote: The best way to report issues is described at http://developer.apple.com/bugreporter/ -- Matt Haffner University of Wisconsin--Madison haffner@astro.wisc.edu Department of Astronomy http://www.astro.wisc.edu/wham WHAM Project http://www.astro.wisc.edu/~haffner/public.key PGP _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... Thanks for the quick reply and great feedback. I'll go ahead and submit a report and relay the details here as well. I've recently submitted a bug to tcl-mac for a minor, but debilitating issue for some Tk widgets on x86_64 with 10.6's included TCL/Tk. The fix has been put into their dev stream, but I was curious what the best mechanism is for suggesting injecting the patch into a future OS X update. Reports submitted there are delivered directly to the engineering teams via the same mechanism that we use to track issues internally. Is it typical for Darwin sources to be updated from external repositories during x.x.n updates? It depends on the severity of the issue. Typically only severe crash/hang/usability issues and security vulnerabilities are addressed via the Software Update mechanism. If not, since it's part of Darwin is a detailed post here the best step, or do I submit to Apple's dev bug reporter. Posting to the list has the benefit of involving a wider audience in the conversation. Filing a bug and referencing the number in your email discussion would be best. Kevin This email sent to site_archiver@lists.apple.com