Hi, Oliver-Rainer Wittmann - Software Engineer - Sun Microsystems wrote:
> Hi all, > > Thorsten Ziehm wrote: >> Hi Mathias, >> >> Mathias Bauer schrieb: >>> Ingrid Halama wrote: >>> >>>> This is not sufficient. Heavy code restructurings and cleanups are >>>> not bound to the feature freeze date, >>> Perhaps they should? And at least as far as it concerns me they are. >>> >>>> but have a great potential to introduce regressions also. I think the >>>> show-stopper phase must be extended in relation to the feature-phase >>>> *and* the normal-bug-fixing-phase. >>>> >>>> Furthermore what does it help to simply let different people do the >>>> nominations while the criteria are not clear? So I would like to >>>> suggest a criterion: In the last four weeks before the feature freeze >>>> only those (but all those) CWSses get nominated that have a complete >>>> set of required tests run successfully. Same for the last four weeks >>>> before end of normal-bug-fixing-phase. We could start with the tests >>>> that are there already and develop them further. >>> >>> The problem is that the usual test runs obviously don't find the bugs >>> that now bite us, most of them have been found by users or testers >>> *working* with the program. Adding more CWS test runs and so shortening >>> the time for real-life testing will not help us but make things worse. >> >> The problem is a bit more complex. The testers and test script writers >> do not have any time for writing new test cases for new functionality, >> they do not have time to check fixed issues in master, they do not have >> time to check code changes in a CWS as much as they should and at the >> end you are right, they do not have the time for real-life testing. >> >> But at the last point I want to relativize a little bit. The QA >> community and the L10N testers find critical problems in DEV build very >> early. Most of the regressions which were reported in the past days on >> the releases list, are regressions in the very past builds. Some of the >> issues weren't identified very early by Sun employees, because they have >> to look in a lot of issues these days to identify the show stoppers. >> > > 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. 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 -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "nospamfor...@gmx.de". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
