Hi, I try to give the discussion some structur, may it's helpfull.
We are discussing 3 questions (may be there are mor ;-)): 1. How to prevent bugs? 2. How to find bugs as early as possible? 3. How to fix known and reported bugs as many as possible and as soon as possible? Everbody knowns that the resources aren't unlimited, so we have to find (new and/or better) ways to solve the problems with our limited resources. Let my try to explain some ideas to find answers to questions above. ad 1.: Preventing bugs is in the first line task of developers. But I think, there are also persons in the community, which are professional software developers and have some experience in techniques of bugprevention. So more communication of that issue can be usefull. (Perhaps a kind of workshop can be a starting point.) ad 2.: IMO a good and trustfull collaboration between developers and QA is needed to test fixes and new code as early as possible and to give feed back to the developers. ad 3.: Here IMO the method of fixing all known bugs to a special issue (like mail merge etc.) is a good practice. Also at that point more an better communication ist needed. Identifing the scopes, which will be approached next, consoldation of the reported issues and so on need a good collaboration and communication between developers an QA. Do good Things and talk about it - inform marketing ;-) So the metaquestion seems to be: How to improve fruitfull communication between the professionals and the community members? This fruitfull communication is also needed to improve the tools used for collaboration and testing. Just some ideas. Michael P.S.: Please excuse my poor english. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
