Hi Mike, thank you for your feedback.
I see the problems you have with the Quality Assurance of OOo. But I do not see, that is a problem of the QA processes. The job of the Quality Assurance is to assure the quality of the software. We have to identify the defects before integration or the regressions or new bugs, when the integration was done. This isn't a productive part of a feature implementation. It is destructive work. The QA has to show the development, what they have done wrong. So it isn't easy for the QA team to find positive aspects in their work, because we have to show, where the product works wrong. But without it, the quality will not increase, so the work has to done. How could the QA get positive aspects from their work. You are right, it is only positive, when your bug which you found or which you worked on is fixed quickly and will be integrated soon. But there are thousands of opened issues. OOo is so big, that it isn't possible to fix all these bugs. The resources are limited - until now. Most of the defects are fixed by Sun developers. The community development want often only fixed their own problem or want to bring in some new features. Bug fixing isn't very interesting, new code is better and everyone in the world can see, what cool new feature is integrated. With the new structure of the QA sites on OOo, we want to collect the experts in QA team. We want to bring them nearer to the Sun team and perhaps we will found someone from the community who is willing to be a Team Lead for an application or an testing area. We want also to bring new members to a higher level of Quality Assurance. The Sun QA team will bring test case specifications on the sites to show how they work on new features. This can be taken to learn the way how to identify problems and find the root causes quicker. Also with the direct contact it will be more possible to identify critical issues easier and quicker to the development team. But this does not mean, that each issue will be fixed. The Sun QA team has the same problem with fixing their bugs as each other on OOo. http://qa.openoffice.org/ The new QA sites are not complete ready and some information will be updated in the very next days. But take a look at it, and if you are interested in, please contact the Team Leads. Please stay tuned, an announcement for the new pages will follow next week. The Sun QA team is a part of the community. We try to do our best, but it isn't possible to do all that work for OOo. Mathias Bauer explained very often on the dev list on OOo, that we need the help to categorize bugs and features. Perhaps I haven't answered all your questions. But as I wrote above, I do not think it is a problem of the QA process. It is a problem of the big project (OOo) and the limited resources. Regards, Thorsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
