New: OpenOffice.org 2.1.0 Release Candidate 1 (build OOE680_m5)

On 25/11/2006, at 1:42 AM, Joost Andrae wrote:

> Release Candidate 1 (build OOE680_m5) has been uploaded
to ftp  
> master. The Linux build already has one known issue
(that is caused  
> by i71899 which will be fixed later in 2.2): the system
integration  
> doesn't work. As a workaround you can fix it by
correcting the  
> symlink in /usr/bin which points to a wrong location.
The problem  
> of the wrong path will be fixed in the next build.
>
> Full localized builds and language packs can be found
at
> http://oootranslation.services.openoffice.org/p
ub/OpenOffice.org/ 
> 2.1.0rc1/
<snip>

I am still trying to come to grips with the TCM, but I think
I have  
myself set up to test RC1 in Vietnamese on Mac OSX (both x86
and PPC).

I will encourage community members to participate, but I
can't  
explain to them how it works until I understand it myself.
;)

As soon as I have Vietnamese Mac OSX builds for m5/RC1, I
will try to  
test them via TCM. I do hope also to get some feedback from
our  
community, as to how the builds work on different
architectures.

from Clytie (vi-VN, Vietnamese free-software translation
team / nhóm  
Việt hóa phần mềm tự do)
http://grou
ps-beta.google.com/group/vi-VN

Hi Clytie,

Clytie Siddall schrieb:
>
> I am still trying to come to grips with the TCM, but I
think I have 
> myself set up to test RC1 in Vietnamese on Mac OSX
(both x86 and PPC).
>
> I will encourage community members to participate, but
I can't explain 
> to them how it works until I understand it myself. ;)
>
> As soon as I have Vietnamese Mac OSX builds for m5/RC1,
I will try to 
> test them via TCM. I do hope also to get some feedback
from our 
> community, as to how the builds work on different
architectures.
Assignment seems to be correct  So you can
start updating results.

But a hint: you assigned *all* scenarios. This would mean
double testing 
of some test cases. E.g. all test cases in  "interop
with MS Office" 
scenario are in the Application scenarios (Writer, Calc
....) as well. 
The same is for "release sanity" this consists of
test cases from 
application and automation scenarios.
The more we test, the better ist is .. but it doesn't make
sense to 
assign testcases twice to one tester. If you assign to
different 
testsers this is very usefull.

André

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org

Thanks for your reply, André. 

On 26/11/2006, at 1:09 AM, Andre Schnabel wrote:
>
> Clytie Siddall schrieb:
>>
>> I am still trying to come to grips with the TCM,
but I think I  
>> have myself set up to test RC1 in Vietnamese on Mac
OSX (both x86  
>> and PPC).
>>
>> I will encourage community members to participate,
but I can't  
>> explain to them how it works until I understand it
myself. ;)
>>
>> As soon as I have Vietnamese Mac OSX builds for
m5/RC1, I will try  
>> to test them via TCM. I do hope also to get some
feedback from our  
>> community, as to how the builds work on different
architectures.
> Assignment seems to be correct  So you can
start updating results.

When the OSX Intel builds for RC1 are available. 
>
> But a hint: you assigned *all* scenarios. This would
mean double  
> testing of some test cases. E.g. all test cases in 
"interop with  
> MS Office" scenario are in the Application
scenarios (Writer,  
> Calc ....) as well. The same is for "release
sanity" this consists  
> of test cases from application and automation
scenarios.
> The more we test, the better ist is .. but it doesn't
make sense to  
> assign testcases twice to one tester. If you assign to
different  
> testsers this is very usefull.

Ah, I didn't realize there was overlapping between those
categories.  
I'll unassign the duplicates. And, if I ever find another
Vietnamese  
person who uses a Mac — I don't know any yet :( — I'll
try to talk  
him or her into participating. 

from Clytie (vi-VN, Vietnamese free-software translation
team / nhóm  
Việt hóa phần mềm tự do)
http://grou
ps-beta.google.com/group/vi-VN