The same happens with the Catalan version. Latest builds don't appear
in the QATrack and we are more than willing to test them!

Regards,

Jesús.

2010/1/11 Martin Srebotnjak <[email protected]>:
> Hello,
>
> please add language "Slovenian" to my name (filmsi) in QATrack, please. We
> will do sanity checks etc. for RC2 i.e. 3.2.
>
> We tried also the full tests of Slovenian RC1 as seen in QUASTe, but due to
> impossibility to upload updated test results the displayed number of errors
> there is misleading, because Vito was adapting the testcases to Slovenian +
> tuning his test environment along the way as he was testing. He did tests on
> OSX and Windows and I did sanity checks on both systems and everything looks
> fine for us (this is no surprise as OOo is 100% localized into Slovenian
> from 1.x version days, we just didn't officially test it). It is time it
> gets also officially released.
>
> I guess my other two colleagues from the Slovenian l10n team (bobe and
> smolejv) already have proper rights and Slovenian language linked to their
> roles?
>
> LP, m.
>
> 2010/1/11 Marcus Lange <[email protected]>
>
>> suso wrote:
>>
>> Hi,
>>
>>
>>  I still need to have QATrack to be turned operative. Could anybody please
>>> give me instructions on how to proceed in order to get RC2 binaries TCM
>>> tested, QATrack approved and then officially released, in this situation?
>>>
>>> Thanks to all the people who is helping us with this! :)
>>>
>>
>> first you need to have a user login for this tool, so that you can add the
>> respective builds you want to test and approve.
>>
>> @Per:
>> Please can you take over?
>>
>> HTH
>>
>> Best regards
>>
>> Marcus
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>



-- 
Jesús Corrius
http://www.corrius.org

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

Reply via email to