On 2009.03.17. 19:56, Mathias Bauer wrote:
Hi,
Oliver-Rainer Wittmann - Software Engineer - Sun Microsystems wrote:
Hi all,
Thorsten Ziehm wrote:
...
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:
thinking about time when bugs are found i got reminded about one issue -
actually getting the dev/testing builds.
i'll admit ignorance about how these things are handled, but that might
also help to understand how many possible testers would see it.
from my point of view, dev snapshots aren't always available fast
enough, and quite often in dev series only every other build is
available to public. of course, this means less testing and testing
later in the development process.
for example, currently supposedly OOO310_m6 is available, public
download - m5
supposedly DEV300_m43 is available, public download - m41
ideally, dev snapshouts would be built & distributed automatically as
soon as possible, and all of them. otherwise testers of development
versions will either always come in later in the cycle, or only
dedicated qa involved people will do testing, who know where/how to get
a more recent dev snapshot - but that probably wouldn't quite qualify as
a sufficient real world usage...
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.
I'm currently investigating the blocker list. Here's a rough summary:
from 77 issues 42 have been introduced before feature freeze (IIRC that
was in DEV300_m39). 9 issues are regression on the OOO310 code line, the
others still are not classified, but I'm working on it. I will follow up
with the complete results later.
Interestingly a considerable amount of showstoppers have been present
already in 3.0.1, some in 3.0 and a very few even in older versions.
Some of them even weren't regressions at all.
An interesting problem is
http://www.openoffice.org/issues/show_bug.cgi?id=100235
This issue was introduced very early (DEV300_m26 or so), but couldn't be
found before we had localized builds.
Regards,
Mathias
--
Rich
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
