Thorsten Bosbach wrote:
> Hi Testers,
>
> I made some changes to the TestTool environment today.
> The details are in the changes mails.
> The changes were tested and reviewed by another person during the last
> week.
>
> I will list them here:
>
> Bug fixing:
> - Open UNO port in OOo on first start
>> http://qa.openoffice.org/servlets/ReadMsg?list=features&msgNo=52
>
> New function for test developer:
> - Function to get the document language
>> http://qa.openoffice.org/servlets/ReadMsg?list=features&msgNo=49
>
> Needed changes because of changes in OOo:
> - Use new API for options path settings
>> http://qa.openoffice.org/servlets/ReadMsg?list=features&msgNo=53
>
> Changes for special tasks:
> - Private environment
>> http://qa.openoffice.org/servlets/ReadMsg?list=features&msgNo=48
> - Custom defined timeouts for starting/closing OOo
>> http://qa.openoffice.org/servlets/ReadMsg?list=features&msgNo=50
> - Enable some framework for valgrind tools
>> http://qa.openoffice.org/servlets/ReadMsg?list=features&msgNo=51
>
> (The links might not jet all work, but should by tomorrow...)
>
> Upcoming changes:
> For releasing OOo 2.1 we will introduce the tag for checkout this week.
> This would mean you will have to provide the tag name 'ooo210' on
> checkout of the scripts for testing OOo 2.1 (OOE680).
>
> On the last release the tag was given after we finished the qa inside
> Sun Microsystems StarOffice testing.
> The change to the last release is, that we will work in parallel this
> time on the release of OOo 2.1 (OOE680) and on the 'normal' master
> SRC680.
> In the meaning of cvs this will be a branch on qa/qatesttool.
> (But you still just need to know that it is handled as 'tag' on
> checkout from cvs.)
Thorsten:

Is there a way that I can get ahold of this so I can check it against
the Mac OS X Power PC and Intel versions?

Thank you.

James McKenzie


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

Reply via email to