On Wed, 27 Apr 2005 20:58:59 +0100, Sophie Gautier wrote > Ha ! and what if he doesn't get an answer ? Wasn't cws done to ease > community developer participation ?
I think it allowed community contributions to be split up into smaller units which will simplify the QA task. > > At the moment QA is not sufficiently documented to be done by community > > members. Once community QA is possible this will help to speed up the > > process. I will try and guess what they do. Looking at a cws, they might ask these questions: - does it meet coding standards? - does it break some other code in any other module? - does it hinder future development? - does it perpetuate something that should be removed? - will it perform correctly in different situations? - does it solve the problem? - will it build correctly on all platforms and all build systems? Probably the work is done by engineers using much intuition based on experience and qualifications, which is not easily documented. > Anyway, what are we doing now ? Is it ok for Laurent to be the QA > representative for this cws ? If I am right, then QA of a cws is a completely different thing from the community QA project. thanks jim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
