On Oct 30, 2007, at 8:49 AM, Laurence Harris wrote: On Oct 30, 2007, at 6:30 AM, Thomas Engelmeier wrote:
On 30.10.2007, at 01:09, Chris Espinosa wrote:
I have to disagree here. As far as a developer is concerned, "Duplicate" IS a black hole.
There's no official way to find out.
ADC sends courtesy emails out to originators of duplicate bugs when the original is fixed.
That would imply that all 108 of my reported duplicates are not fixed, which in turn would imply Mail 3.0 is not in an state where I can read this list and send this mail.
He means the person who filed the original bug is notified. Anyone who filed a duplicated after that is on his own. And for the record, it isn't always a courtesy e-mail. Sometimes they downright pester you to verify the fix. They even called me one time to verify a fix, which I thought was cool.
No, Larry, I meant what I said. Most developer-originated bugs that I mark as Duplicate get a notation like this put in them by ADR:
4/4/03 4:51 PM ZEENAT SUBEDAR: Added 'ADR Duplicate Issue' keyword to original bug, so we can notify this developer of resolution when original issue is closed.
(the keyword has changed over the years). When an original issue is closed, ADC sends a batch courtesy notification to all ADC member accounts that have a duplicate filed against it. There are some holes in this scheme (as I note in my response to Thomas) but there is a process in place to notify developers when issues they report have been resolved, even if they're initially marked as duplicates of other issues.
Further discussion of this really has to take place with ADC, not the Tools team, as we have little influence over ADC programs and practices.
Chris |