• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: OT: Radar (was Java, Xcode, CodeSense, java docs, etc.)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OT: Radar (was Java, Xcode, CodeSense, java docs, etc.)


  • Subject: Re: OT: Radar (was Java, Xcode, CodeSense, java docs, etc.)
  • From: Ricky Sharp <email@hidden>
  • Date: Wed, 29 Sep 2004 11:49:21 -0500

On Wednesday, September 29, 2004, at 11:18AM, Bryan Pietrzak <email@hidden> wrote:

>
>On Sep 23, 2004, at 4:26 PM, Toni Trujillo Vian wrote:
>
>> Martin,
>>
>> As one of the Directors of Engineering at Apple, I can guarantee you
>> that your time spent filing bugs is not useless.  We can not respond
>> to all the bugs in our queues but do use Radar as an important tool
>> when determining what will be fixed from release to release.  I view
>> bugs in Radar daily and my teams manage their work queues by what has
>> been filed.
>>
>> You should know that we appreciate you talking the time to use our
>> products and report problems as you find them. This is one of the ways
>> Apple can we move the products forward to meet our customers needs.
>>
>> Thank you,
>> Toni Trujillo Vian
>> Director, Interactive Tools
>
>Apple should investigate some automated processes around the handling
>of Radar reports.
>
>Maybe just automated e-mail notices when a bug report is...
>
>(a) FIRST reviewed by anyone at Apple (that lets us know that a real
>live human being is looking at it)
>(b) marked as a duplicate with reference back to the original radar (so
>we can ask DTS to follow-up)
>(c) marked as closed for not able to repro or not a problem (due to
>design decision, etc.). This let's us know that we didn't make our case
>well enough :)
>
>
>Also...PLEASE PLEASE enhance Radar so that when Apple employees are
>adding comments they can have some checkbox to indicate the comment
>should be sent on to the developer who filed the bug report. I've lost
>count of the times that I've talked to Apple folks about a given bug
>report only to have them say something like "yeah, six months ago an
>engineer noted that the problem is xyz and that until it's fixed the
>developer can workaround it with abc". I mean if the Apple engineer had
>a checkbox in Radar that said "Send Comments To External Developer"
>this alone would solve a LOT of the griping about the Black Hole That
>Is Radar. (Assuming the Apple engineers would use it!)
>
>Lastly, I understand the sensitive issue of not wanting to give away
>information about when something was fixed as it can feed the rumor
>mills about unannounced products, etc. But, as it stands now, Apple is
>hurting its developers with its current 100% blackout on information
>sharing. Please, just try to shift the balance towards us a little bit.
>Doesn't have to be 50/50, even 90/10 would be a huge improvement.

I strongly second this.  I filed an enhancement request over a year ago to allow developers (including Apple) to mark a bug as being "public".  This would allow anyone to see details on a particular bug.  But alas, nothing was done with that bug and it was simply closed.  I was never given an explanation as to why.

If notes are sensitive, they can easily be hidden if the submitter and/or Apple deems so (as Brian mentioned, a simple checkbox can be used).  Furthermore, every ADC member has a Person Number (ID).  So a system could easily be added to query the developer level.  For example, as a Select member, if I submit a bug against Tiger, any other Select (or Premier) member could also potentially look at that report.  Any other developer would simply not see the bug/notes.

Finally, I feel it's a shame that we developers have to resort to using mailing lists to vent like this.  As I wrote above, filing a enhancement request did no good.  Also, on a slightly related topic, I filed a DTS incident in hopes that a dedicated mailing list to discuss Tiger could be started.  I did get an incident "refund", but no mailing list exists to date.  So beyond enhancements & incidents, what's the best channel to use to make sure Apple knows just how many of us are affected by the poor systems currently in place?

Rick Sharp
Instant Interactive(tm)

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: OT: Radar (was Java, Xcode, CodeSense, java docs, etc.)
      • From: stephane sudre <email@hidden>
    • Re: OT: Radar (was Java, Xcode, CodeSense, java docs, etc.)
      • From: Finlay Dobbie <email@hidden>
References: 
 >Java, Xcode, CodeSense, java docs, etc. (From: Brent Gulanowski <email@hidden>)
 >Re: Java, Xcode, CodeSense, java docs, etc. (From: Rob Lockstone <email@hidden>)
 >Re: Java, Xcode, CodeSense, java docs, etc. (From: Martin Kahr <email@hidden>)
 >Re: Java, Xcode, CodeSense, java docs, etc. (From: Toni Trujillo Vian <email@hidden>)
 >OT: Radar (was Java, Xcode, CodeSense, java docs, etc.) (From: Bryan Pietrzak <email@hidden>)

  • Prev by Date: OT: Radar (was Java, Xcode, CodeSense, java docs, etc.)
  • Next by Date: IOKit driver creation problem
  • Previous by thread: OT: Radar (was Java, Xcode, CodeSense, java docs, etc.)
  • Next by thread: Re: OT: Radar (was Java, Xcode, CodeSense, java docs, etc.)
  • Index(es):
    • Date
    • Thread