{Dangerous Content?} Job offer

Christian Robottom Reis kiko at async.com.br
Thu Oct 23 11:45:50 UTC 2003

On Wed, Oct 22, 2003 at 03:26:14PM -0500, Steven Suson wrote:
>    As for what an ECN is.... Upon successful completion of an ECR (i.e. 
> it was FIXED), a board decides what actual changes need to be made to 
> schematics, software, hardware, etc. Once this is done, email 

I'd like to understand what sort of artifacts this "board decision"

> notifications must be sent out to all individuals on the ECR (i.e. bug) 
> email list, as well as a predetermined list of others (managers and what 
> not), therefore formally notifying all of these as to the actual 
> solution to the problem, and making it a matter of record.

So should the ECN be mapped as a completely new bug, or just an extra
step in the lifecycle of the ECR? What sort of data (attachments,
comments, other structured/enumerated fields) does the ECN need to have
that aren't relevant to the ECR (i.e., wouldn't make sense in the main
ECR page)?

Take care,
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331

More information about the developers mailing list