eric.bachard, 17-03-2007 10:42:
Caio Tiago Oliveira a écrit :
[...]
We should discuss the process of QA'ing for Mac OS X.
Indeed. Historically, and since the begining Mac OS X port is very
dynamic with QA - AFAIK, german, japanese and french communities are -
and I'm sure a high quality work is already done. ( Many thanks to the
people helping us BTW ! )
So what does not work ?
I meant: how to integrate the QA on Mac OS X with some non-Mac related
CWS's.
If someone is touching a file with Mac specific code and modifying the
non-Mac specific part, he could break it on Mac and don't notice.
It's something like: if there is a high chance of breaking something on
Mac OS X, it should be included in the list of platforms tested on the CWS.
Of course the Mac team should seek for volunteers willing to do QA on
some CWS's.
I'm not sure to be enough precise, but every time we try to discuss
about QA points in Mac OS X IRC meetings ( see
http://wiki.services.openoffice.org/wiki/Mac_OS_X_Port_Meetings ) , we
have not too much informations, and sometimes we have nothing at all.
This is not a very big issue, but a better coordination would help. Of
course, any suggestion / contribution is welcome :)
Don't to enforce anything, but would be good to have Mac OS X users
willing to help with the QA of some global CWS's.
We already have, but we lost some QA-testers ( at least on french
project) with repeated QA for rc1 .. to rc7 : all people are volunteers,
and do QA after the Office hours, often late in the night, and ask them
to redo several time the same test was not a good option.
I was talking here mainly about QA on CWS's (of course the test on the
RC's is still very important).
Buildbots are doing some kind of QA on CWS's for Mac, but it's only
about the build process.
I know human resources is an issue, but it's true for other ports as
well and have more Mac testing on the overall product is good, since you
can find another issues earlier.
You can decide to focus on the Aqua port before considering all of this,
but a mature port should consider finding the issues before have them
getting integrated, so having a stable product each milestone.
It's better for testers, developers, everyone.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
