Hi Joerg,
Joerg Barfurth a �crit :
Hi Eric,
But if that list contained all registered OOo members, it would ne unusable ...
Ok...that's the reason why I've asked here : I was not sure it works...
We also have a gatekeeper, who watches for process violations and may stop a CWS even after QA approval, if the QA was not done according to the rules.
Yes
Things to do include (but may not be limited to):
- Check that all the conditions listed as 'mandatory' for setting the CWS to 'Ready for QA' in the CWS policies are fulfilled.
Ok, sure this cws is ready for QA
- For features: create a testplan (we don't have a public process, nor any process for OOo-only features, for this yet)
In #i47107# , the testplan is simple and given by the content of the issue.
- Check that all issues on the child workspace are really fixed and features are implemented as specified and announced.
For now, changes are tested on both :
x86 :
Linux Intel m95 (laurent)
PowerPC
Linux PPC m96 (me) Mac OSX m93/m95/m97 (me)
But not yet on Windows nor Solaris nor Sparc. I'll ask a last test, thinking this will probably be sufficient.
IMHO the qa project should start working on defining and documenting this in a way that makes experienced members of the qa project eligible as CWS QA Rep. But I have the impression that atm Sun QA still needs to be involved.
Cannot give an answer...I'm yet young with cws QA, and learn every day. Thank you for your answer :-)
Regards, eric bachard
--
eric bachard <[EMAIL PROTECTED]>
Francophone OpenOffice.org Commmunity developer (Linux PPC / Mac OS X / X11)
See : <http://fr.openoffice.org>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
