Hi Oliver,
thanks for the data.
Oliver-Rainer Wittmann - Software Engineer - Sun Microsystems schrieb:
IMHO, we do not find critical problems (show stoppers) in DEV builds
very early, only half of them are found early according to my experience.
Some data about the show stoppers, which I have fixed in the last days:
ISSUE INTRODUCED IN FOUND IN
i99822 DEV300m2 (2008-03-12) OOO310m3 (2009-02-26)
i99876 DEV300m30 (2008-08-25) OOO310m3
i99665 DEV300m39 (2009-01-16) OOO310m3
i100043 OOO310m1 OOO310m4 (2009-03-04)
i100014 OOO310m2 OOO310m4
i100132 DEV300m38 (2008-12-22) OOO310m4
i100035 SRCm248 (2008-02-21) OOO310m4
This issue is special, because it was a memory problem, that by accident
was not detected. Thus, it should not be counted in this statistic.
Looking at this concrete data, I personally can say that we find more or
less half of the show stoppers early.
Half of them is in my opinion a good quote. But this doesn't mean, that
we do not have to improve it. And one point is, that features has to be
checks more often in the master. Perhaps with automated testing or with
regular manual testing or real life testing. But this costs resources
and this is the critical point. Most of the QA community is also part of
the L10N community. This mean they are working on translation, when OOo
run into a critical phase like Code Freeze, where most real-life testing
is needed.
So it isn't easy to fix. Therefore I think 50% is a good quote under the
knowing circumstances.
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
