Friday December 14th, 2001
As you may have noticed, we've taken the forums down, as we are hitting our bandwidth limit with them. We're working on getting them up and running again as soon as possible.
#43 Root cause analysis
by SubtleRebel <firstname.lastname@example.org>
Tuesday December 18th, 2001 9:45 AM
You are replying to this message
>Root cause analysis is a standard quality technique which applies equally well to any project, and is not confined to software. It is an attempt to analyze problems to find out which components of the overall system they have in common. Once a set of data on problems is built up, it becomes possible to find through statistical methods which components are tending to cause the most problems. The reasons for the instability caused by that component can then be analyzed in detail by QA engineers, and they can formulate proposals for changes to prevent or minimize further problems from that component.
You have still failed to explain what you think it would accomplish regarding Mozilla.
I never said that I did not understand what root cause analysis was, nor have I ever questioned the general usefullness of the process, but what I did say is that I do not think it would result in any signifigant improvement in the project.
You seem to have a problem with the whole open source development process. If you were to do a root cause analysis of Mozilla, I think you would conclude that the procedures need to be more like a closed source development project, but that just is not practical for an open source project with such distributed development and resources.