Re: Apple Bug no response
> You might get an automated email when a future build is available asking you > to re-test. You may get a note that your bug is a duplicate. You may never > get a response at all. Or… …yesterday I got feedback asking if a bug I reported in an early *Yosemite* seed was resolved in the latest software. It was in fact resolved before Yosemite went GM (September, 2014, IIRC). ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Apple Bug no response
> On Mar 9, 2016, at 6:52 PM, Michael David Crawford> wrote: > > I have a bug in Apple's sample code that would be a trivial fix, that > has been open for eight years. > > By contrast I've reported a few kernel bugs. Each was fixed in the > very next build. My experience is similar. I've reported accessibility API bugs since 2002 that have always been fixed immediately. Maybe that's because accessibility is important to Apple (as a lawyer, I can tell you that it is very important legally); maybe that's because they know I'm experienced on accessibility issues; maybe that's because the accessibility team is particularly interested in getting things together. Bugs that I've reported in other areas sometimes get responses, sometimes they get fixed, other times they get ignored as far as I can tell. So, Apple is a big organization, with lots of different departments, and it's hard to see consistency. The one thing I'm very confident about is that well written bug reports get better attention than poorly written bug reports. -- Bill Cheeseman - wjcheese...@comcast.net ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Apple Bug no response
I have a bug in Apple's sample code that would be a trivial fix, that has been open for eight years. By contrast I've reported a few kernel bugs. Each was fixed in the very next build. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Apple Bug no response
> On Mar 9, 2016, at 1:32 PM, Trygve Indawrote: > > I have an open bug report > > How long should I expect to wait for a response? My experience with issues. If you have a graphics related bug (OpenGL, Core Animation, Graphics Adapter Specific) they get on it right away and you will get a response. If you have another kind of bug you will generally wait and hear nothing. If you submit a technical support incident you will get a response. --Richard Charles ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Apple Bug no response
#4145901 .. June 12, 2005 > On Mar 9, 2016, at 4:02 PM, Gary L. Wadewrote: > > My oldest open bug will be 10 years old by WWDC 2016. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Apple Bug no response
My oldest open bug will be 10 years old by WWDC 2016. -- Gary L. Wade (Sent from my iPhone) http://www.garywade.com/ > On Mar 9, 2016, at 12:50 PM, Eric E Doleckiwrote: > > I have bugs that have celebrated their fifth birthdays. Fire and forget. > > Sent from my iP6+ > >> On Mar 9, 2016, at 3:44 PM, Hunter Hillegas wrote: >> >> You must be new here. ;-) >> >> You might get an automated email when a future build is available asking you >> to re-test. You may get a note that your bug is a duplicate. You may never >> get a response at all. >> >> I have many open bugs from years back which usually either means the issue >> is still out there or it was fixed but the screeners didn’t wire up the bug >> in a way that they know my issue was resolved. >> >> Apple has said (Craig F. on The Talk Show recently) that this is a place >> they know they have room to improve. >> >>> On Mar 9, 2016, at 12:32 PM, Trygve Inda wrote: >>> >>> I have an open bug report >>> >>> How long should I expect to wait for a response? >> ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Apple Bug no response
I have bugs that have celebrated their fifth birthdays. Fire and forget. Sent from my iP6+ > On Mar 9, 2016, at 3:44 PM, Hunter Hillegaswrote: > > You must be new here. ;-) > > You might get an automated email when a future build is available asking you > to re-test. You may get a note that your bug is a duplicate. You may never > get a response at all. > > I have many open bugs from years back which usually either means the issue is > still out there or it was fixed but the screeners didn’t wire up the bug in a > way that they know my issue was resolved. > > Apple has said (Craig F. on The Talk Show recently) that this is a place they > know they have room to improve. > >> On Mar 9, 2016, at 12:32 PM, Trygve Inda wrote: >> >> I have an open bug report >> >> How long should I expect to wait for a response? > > > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/edolecki%40gmail.com > > This email sent to edole...@gmail.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Apple Bug no response
You must be new here. ;-) You might get an automated email when a future build is available asking you to re-test. You may get a note that your bug is a duplicate. You may never get a response at all. I have many open bugs from years back which usually either means the issue is still out there or it was fixed but the screeners didn’t wire up the bug in a way that they know my issue was resolved. Apple has said (Craig F. on The Talk Show recently) that this is a place they know they have room to improve. > On Mar 9, 2016, at 12:32 PM, Trygve Indawrote: > > I have an open bug report > > How long should I expect to wait for a response? ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Apple Bug no response
On Mar 9, 2016, at 2:32 PM, Trygve Inda <cocoa...@xericdesign.com> wrote: > > I have an open bug report > > rdar://24316348 > > Apple asked for an example to reproduce which I sent on January 27, but I > have heard nothing since. This is a fairly simple bug (NSTextFields can't > fully justify on 10.11). > > How long should I expect to wait for a response? The Apple bug reporter is a means for getting information _in_ to Apple, not out to developers. You won't hear from them unless/until a) they want more information from you (like the example they requested), or b) they have a new seed release of the OS which they believe has fixed the issue and want you to test and report back. You can update your bug report with a request for status and they should give you that, although it will probably be something like "the issue is still being investigated". You can open a developer technical support incident to ask for a workaround, if they know of one. Regards, Ken ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Apple Bug no response
I have an open bug report rdar://24316348 Apple asked for an example to reproduce which I sent on January 27, but I have heard nothing since. This is a fairly simple bug (NSTextFields can't fully justify on 10.11). How long should I expect to wait for a response? Thanks, Trygve ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com