RE: Revisiting NSTextView bugs in Interface Builder (rant about BugRe porter)
RE: Revisiting NSTextView bugs in Interface Builder (rant about BugRe porter)
- Subject: RE: Revisiting NSTextView bugs in Interface Builder (rant about BugRe porter)
- From: Ricky Sharp <email@hidden>
- Date: Tue, 11 Jan 2005 06:38:14 -0600
On Monday, January 10, 2005, at 11:07PM, Erik M. Buck <email@hidden> wrote:
>It was explained to me once that internal to Apple, the complete
>explanation, status, planned resolution if any, schedule for fix,
>responsible person, etc. is available to engineers.
I know in the past that you could contact email@hidden in order to ask about the status of a defect. Probably still is the case. I've never wrote in asking about one that had a status of closed/duplicate, but it's worth a shot that you may be able to obtain the status of the original.
FWIW, I had filed a bug (over a year ago I believe) asking to have a system in place to let bug submitters "mark" their defect as being "public". While Apple would definitely have the right to "demote" such public info back to being private, this could offer at least more information for other developers (e.g. others could see my test cases or what systems I had the problem on).
I was told that they are looking into such a system, but it pretty much ended there.
Personally, what I'd really like to see is a system tied to the developer ID. This would allow, for example, all those with seed access to subscribe to mailing lists that could discuss NDA items (e.g. Tiger) as well as to be able to see bugs about NDA items.
--
Rick Sharp
Instant Interactive(tm)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden