Thorsten Ziehm <[EMAIL PROTECTED]> writes: > The team which worked out the specification process know that the > specifications are not in the highest quality now. This is a learning > process for each member on the specification (User Experience, > Development, Quality Assurance and Documentation). So each team makes > errors know. But the errors are lower than without having a process, > like in OOo 1.1.x time frame. > Hi Thorsten,
I'm not sure whether having specs/not having specs in and of itself has influence on the product quality. A spec only describes what should be/what has been implemented. Ultimately, the QA is the gateway to the main trunk, thus, their way of working and their means of testing (and their ability to actually exercise hidden functionality) determine what enters the master. For Sun-developed features, I'm absolutely on the same page with you (simply because user experience does better UI than me, and Liz does/did come up with better strings than me - by far. Let alone the fact that a lot of people have then been thought about the feature, and provided their feedback). But for community development? It's basically a take-it-or-leave-it, isn't it? Take the feature as-is, or don't take it. Having a spec tacked onto it does not change the feature at all - it's there, already. Providing means for QA and help to actually _understand_ what's been sent to them is of course non-negotiable - but I would tend to call that documentation, not spec (because the formal requirements are much more relaxed). > You can take nearly each of the new specifications and the > corresponding CWS. You will see, that very often bugs were written > after the CWS go into the QA for the first time. > I don't think this is a valid argument here - it is a normal part of the CWS process, and even the prime purpose of QA, to find issues in a CWS before they hit the master. Be it with or without specs. And of course, a severe CWS issue is missing/incomplete documentation of what has been done in it. Cheers, -- Thorsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
