Hi Mathias, > At the risk of being caught ignorant: should feature/changes mails on > these lists be posted before the CWS is approved? I think that odds > aren't low that something might get changed after handing over the CWS, > especially in case of new developers.
AFAIK policies require mails to be sent when the CWS does to QA - which in fact might not make that much sense. > Perhaps we can distinguish between "preliminary" and "final" > announcements, the former is sent when the CWS is handed over from the > developer, the latter when the final step ends with the CWS approval. I'd prefer an ability to add feature mails in EIS which are not yet sent. That is, I would like to fill out the form for the feature mail, and press some "Send Later" button. The mail would then be associated with the CWS, and only sent when the CWS gets approved/nominated/integrated (whatever). QA can still look at the mails, and development can change them before sending, if necessary. The additional advantage of such a feature - completely independent form the current discussion here - is that for large CWS, you do not need to manually track all the chances (esp. API changes) you did therein. You can write them when they happen, and they're all sent at once when the CWS is finished. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
