Hi Bernd, On Thursday, 2006-11-16 16:08:34 +0100, Bernd Eilers wrote:
> The questions where I am currently unsure about are the following: > > 1.) can automatically move all featuremails/api-changes from state draft > to state finished when the state of the CWS moves to state 'ready for > QA' or should we do that when the state of the CWS moves to 'integrated' If integrated. > or if should we not do any automation at all and leave it up to the > developer to change the state of the featuremail and apichange only? After integration the feature as desribed by the featuremail is final, if it wasn't, a new CWS would be created and the feature be changed, with a "feature changed" mail, if needed. There is no sense in keeping the featuremail in draft status and burden the developer with having to remember to set it to final. > 2.) Can there be a case where a feature mail is "finshed" but must still > be changed You never know, it might happen. For example if a description is wrong or important information missing. > and what should happen in this case regarding the > mailinglist, resend the featuremail? Yes. > If for 1.) we would decide to declare things final only at integration > Problem 2.) is not there because a change in the feature would be done > in a new CWS and a new featuremail would be needed there for it. True if the feature needs changing, not true if only the featuremail needs changing. > On the other hand QA must have information about the feature when the > CWS is 'ready for QA' and we can not require that anyone in QA get´s > familar with RSS feeds. If the featuremail is a feature of EIS, assigned to the CWS and a task and readable for everyone, the information may always present via the web interface. No need to make it available only in RSS feeds. > Maybe this can be resolved by having 3 states 'draft', > 'published' and 'final' and moving to published with sending to > mailinglist when state changes to 'ready for QA' and moving to > 'finished' with or without publishing to mailinglist also when CWS state > changes to 'nominated'. No, that's just confusing. The featuremail gets final and is published when the CWS is integrated. We don't need extra states that complicate things. Maybe with the possibility for the developer to send out extra draft mails before integration, if needed. Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to the [EMAIL PROTECTED] account, which I use for mailing lists only and don't read from outside Sun. Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
