From: Thorsten Ziehm <[EMAIL PROTECTED]> Subject: Re: [qa-dev] New Lead at the QA project - Welcome Maho! Date: Wed, 06 Dec 2006 11:29:44 +0100
> [1] : http://blogs.sun.com/GullFOSS/entry/what%27s_up_in_the_openoffice.org This blog entry is really interesting. > They confirming issues, making L10N QA, releasing the L10N builds and making > QA for platforms which are not supported by Sun. But the mass of daily work > on the product is done by the Sun QA team. Check fixed issues in a CWS, check > the fixes in the master build (developer snapshots) or what ever, why this > work cannot be realized in the community more than now? One unclear issue can > be the questions 'who should organize that work?' and 'who should be > responsible?'. Also I'm thinking about such kind of things. I always choose Pavel Janik as QA representable for my small CWSes. and the number of such person is striclty limited. We must increase such persons. Currently Jack Low and I are providing FreeBSD packages, and MacOSX packages. L10N QA is much more difficult. Providing developer snapshot builds are mandatory. For example, Japanese specific issue XXXXX ``has been fixed in SRC680_mXYZ'' and usually reassign to reporter. But currently reporter should build (for example) Windows Japanese! version of SRC680_mXYZ and verify. but it may take too many resources. I have been thinking about buildbot, like specify language and target milestone and platform. Then it provids package for serious testers. (All of you might thinking about it) or cws tester; checkout one's cws, provide diffs for cws anchor and provide buildablity for GNU/Linux, Windows, and Solaris. Then run first.bas and topten.bas. if no errors, nomination process becomes much faster. Who should be responsible? I have no idea. Idea itself is simple and in theory, it is apparently possible. but practically impossible (who should pay for it?) . My first attempt is writing documents for everyone. Let all the people know QA process, how to do QA etc. Caio Tiago Oliveira told me that asking for NL for QA is important. He is also right. A lot of things to be done... -- NAKATA, Maho ([EMAIL PROTECTED]) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
