Thorsten:

Thank you.  I use MacCVS to retrieve the updates and I think I did get ooo210.
However, it did not appear to do the UNO call before calling the first instance 
of 
OpenOffice.org 2.1.  Is this to be expected or was I incorrect in this 
assumption.
The UNO problem that I submitted still exists in testtool and only appears 
after the
system parameter scan.  I can still use 2.0.3 to run testtool and the automated 
QA
but it will be removed aftet the release of 2.1 from most of the mirror sites.

James McKenzie
Mac OS X QA/Test Team Lead

-----Original Message-----
>From: Thorsten Bosbach <[EMAIL PROTECTED]>
>Sent: Nov 9, 2006 4:05 AM
>To: [email protected]
>Subject: Re: [qa-dev] TestTool: which scripts to use to test OOo 2.1 (RC)
>
>James Mckenzie wrote:
>> Thorsten:
>> 
>> Checkout command should be:
>> 
>> cvs -z3 -d pserver:[EMAIL PROTECTED]:/cvs co qatesttool ooo210
>> 
>> Correct?
>>
>
>no,
>
>cvs -z3 -d pserver:[EMAIL PROTECTED]:/cvs co -r 
>ooo210 -P qa/qatesttool
>
>> I have started QA for M2 (once it is built) to check the testtool problem 
>> with the Mac OS X Intel releases as there is an open issue with this process 
>> and to make sure that the work around does not break.
>> 
>> Thank you.
>> 
>> James McKenzie
>> Mac OS X QA/Test Team Lead
>> 
>> 
>> -----Original Message-----
>> 
>>>From: Thorsten Bosbach <[EMAIL PROTECTED]>
>>>Sent: Nov 8, 2006 7:19 AM
>>>To: [email protected]
>>>Subject: [qa-dev] TestTool: which scripts to use to test OOo 2.1 (RC)
>>>
>>>Hi Testers,
>>>
>>>to test the release of OOo 2.1 please checkout/update your
>>>scripts with the tag: ooo210
>>>
>>>The scripts are currently worked on.
>>>So you should update your scripts once a week.
>>>
>>>The HEAD will now be used for SRC680 changes.
>>>
>>>cheers
>>>Thorsten
>>>
>>>-- 
>>>*******************************************************************
>>>Thorsten Bosbach                             Sun Microsystems GmbH
>>>Quality Assurance Engineer                   20097 Hamburg, Germany
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to