Approve a CWS
It looks like very simple to approve a Child Work Space (CWS). It is only to set all issues in a CWS to status 'verified' and select 'approved by QA' for the CWS in the Environment Information System [[EIS]). Is this really enough?!
The following information should be used to make Quality Assurance at a CWS and not to change the status of issues and CWSs only. It is essentially to still archive success with OpenOffice.org that the quality could be hold - better if the quality could be extended. This does not mean that OpenOffice.org will not have any bug. No, that is illusively. But new Features and Bug-fixes should integrate without Regressions and the quality should be always able to release.
The following information and links looks a strict and there are Processes which should be kept. But without Processes it is not possible to hold our highest goal – Quality. The customers do not want to have more and more features only, they want them in a high quality. Why otherwise so many Software products and other products have to shift the release dates very often.
The Processes are easy to understand, because an Action list, a Check list and Flow Charts exists. They help to do not forget any activity at CWSs or Issues in a CWS.
Feedback is welcome! Do you think something is wrong or can be deleted. Do you think something should be added or changed. Please make the changes by your own (it is Wiki!) or discuss it in the QA mailing list email@example.com.