Hi Kendy,

Jan Holesovsky schrieb:
Hi Mechtilde,

On Tuesday 18 of May 2010, Mechtilde wrote:

In my view there are different problems.

1. the different build environments, not only ooo-build or vanilla. Each
distri has its own environment with some small differences.

Sure, that is a challenge, but of course it is the package maintainer's duty to fix those.

2. the more or less missing QA-Process.

Not sure what are you talking about? Are you saying that go-oo has no QA process? - that would be a complete news to me :-)

The fact that we differ in the development style (everyone commits the patches directly to the main repository, no CWSes, and the possibility for bugs coming from integration/merges of various CWSes), does not mean that we do not have a QA process.

We have a tinderbox that notifies committers of wrong commits, we release betas in timely manner, have quite an extensive test plan (in our Testopia), run qatesttool during the beta phase & analyze the results, have a large set of documents for regression testing, etc. Oh yes, I must not forget the bug triage of the new bugs which guarantees the initial treatment of the new bugs in up to a (working) day or two.

Mechtilde and you are talking about different QA processes. What you
are writing is developer orientated testing. This is done for OOo often
before a CWS goes to a QA community member. So the manual testing and
the regression testing on UI level is missing in your processes. And
most of the community members in the QA project are doing only manual
testing on UI level. So one major part of Quality Assurance (or QA
management) for Software is missing in your process.

I talked about the complexity of Quality Assurance for OOo on the
OOoCon in Beijing. If you are interested in you can see the video
or can take the presentation from :
http://blogs.sun.com/GullFOSS/entry/the_video_the_complex_world

Thorsten

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to