> From: Sophie Gautier <[email protected]>
>
>Hi all,
>
>I didn't add Mox in copy as my questions are on the QA process for cws.
>Mox Soini wrote:
>> Hello all,
>>
>> I'm looking for someone who is willing to do QA of mox01 CWS.
>>
>> This CWS is for support of "Paste and Match Style", i.e.:
>>
>> Menu item "Paste and Match Style" under "Paste" menu item in "Edit"
>> menu Shortcut key: CTRL-ALT-SHIFT-V on Windows/Linux,
>> Cmd-Option-Shift-V on Mac
>> The changes are in sw, officecfg.
>
>I would like to help here but I don't know how, so it won't be for this
>time. However can somebody help me to learn ?
>What I've seen on the wiki is that the first thing I need is to build
>the cws.
>Can I use EIS > Termite > Buildbot > Recent build > checking install set
>to get my own installset under Termite Install Sets page ?
>Then, this page should be relevant:
>http://wiki.services.openoffice.org/wiki/CWS_Checklist_for_QA_responsibilities
>Another question, the cws is not mark help relevant, does it mean that
>id doesn't need to be documented in the help or that the QA resp has
>also to check for this information ?
>
>Thanks in advance for your answers and time
>Kind regards
>Sophie

I'll provide links to QA installsets in the cws. Due to problems with
tinderboxes themselves, only Mac installset is available right now:
http://termite.go-oo.org/install_sets/MacIntel-1923-mox01-install_set.zip

I also marked the CWS checkbox for help stuff. The code should have
the support for help id already.

...

As a possible QA person, I think you could just follow
http://wiki.services.openoffice.org/wiki/CWS_Checklist_for_QA_responsibilities
and check that this enhancement works as expected.

Ultimately it's the responsibility of the module owner (in this case
sw / writer => [email protected]) to check that the code is
architecturally ok.

BR,

    Mox

-- 
Olet miten teet

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to