Hi Martin, Martin Hollmichel wrote:
I suggest that we make this cws policies official on July 11th if there are no objections until then.
I have modified some things in the Wiki without changing or deleting the content or the meaning of it:
- We should use the common wording in the community 'issue' instead of 'task' - we have more than one specification: (functional) software specification; test case speification [I have added the links to the chapters inside the Wiki] - Bullet lists are fine but you have priorized the issue categories and I have used an ordered list to make it more clear - A "bug fix"? A "fix" is IMO the same (fixing something that goes wrong...); removed the word bug because a fix could also be something that makes an existing behaviour faster/more efficient/....
- added links to QA rules, Gatekeeper, EIS, ....
If these changes get accepted I propose to exchange the "Level of impact" in the EIS application accordingly to the new categorization of cws in the policies.
From my point of view more clear than in the past. Cu, Jogi http://qa.openoffice.org/qatesttool http://wiki.services.openoffice.org/wiki/User:Jsi -- Sun Microsystems GmbH Joerg Sievers Nagelsweg 55 Quality Assurance Engineer 20097 Hamburg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
