Re: Bug tracker suggestion.
Re: Bug tracker suggestion.
- Subject: Re: Bug tracker suggestion.
- From: Lance Saleme <email@hidden>
- Date: Thu, 17 Feb 2005 11:49:12 -0800
Having been on both sides of the fence on this issue...
There is a reasonable compromise solution that can help the majority of
those rediscovering bugs, but costs a little time for the person(s)
reviewing the bugs as they get into the system on Apple's side...
Rather than open up the entire bug database and allow rampant searching
by any developer it might work as well to maintain a separate FFB
(Frequently Found Bugs) list that contains (at least) the reproducible
cases so it can be searched. No information about the originator of
the bug, company, etc. would be displayed.
Info on the bug...
- The unique bug number
- The common title
- A description
- One or more reproducible cases (for searching)
- The current resolution / workaround / status
That would be enough for others to move on with their work.
NDA bugs can be excluded or scrubbed for public viewing. Either way
the core problem is addressed without violating the security of the
full bug database. The bug need not be moved into this FFB list until
it is officially confirmed to exist and/or duplicates are logged
against it.
This, of course, means more work for someone at Apple, but the cost of
lost productivity (rediscovering existing bugs) in the active developer
community is pretty high in comparison.
Just some proactive thoughts on the issue,
Lance
On Feb 17, 2005, at 11:25 AM, Chilton Webb wrote:
Hi John,
On Thursday, February 17, 2005, at 12:55PM, John Stiles
<email@hidden> wrote:
Many people file bugs that are confidential in nature?for example,
imagine if Blizzard needed to file bugs related to World of Warcraft
before the Mac version was publicly announced. (I don't remember if
this was actually the case, but it's certainly possible.)
It would be very difficult to coordinate this unless it was an
"opt-in"
system.
Even still, I think Apple has a vested PR interest in keeping the lid
closed on this sort of thing.
This is a good point. I know of at least one bug I've filed that was
for a confidential project. But damn, searchable bug reports would be
awesome.
For example, imagine the time you'd save if you knew that you can't
pin the cursor on a multi-monitor setup as of 10.3.7? I kid. But if
the archives were searchable, at least you'd be able to know if
someone else found that to be true, and if it's been fixed in an
upcoming OS update.
So how about a checkbox for 'Private--do not include this bug report
in the publicly searchable archive' on the web form?
-Chilton
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
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