Hi Mathias,
Mathias Bauer a écrit :
[...]
I have just outlined a "skeleton" of what I could imagine as (dream of?)
a localization process. The nasty details will be interesting to
discuss. I think that the less steps we have between the files that we
are using for a localized build, and what a l
Sophie wrote:
>> Whether help content must be part of a feature CWS or
>> not should be seen in the general context of how we want to localize it.
>
> Not only, sometimes changes are not documented because the corresponding
> CWS has not been mark help relevant, having an issue in the CWS task
Jörg Jahnke wrote:
> Hi Mathias,
>
> Mathias Bauer schrieb:
> ...
>>
>> Currently the way how localizations get into OOo is very inefficient. At
>> some point in time a "deadline" is reached and a whole bunch of
>> localizable content is exported from the source tree and handed over.
>> Localize
Helge Delfs - Sun Germany - ham02 - Hamburg wrote:
> Hi,
>
> On 09/23/09 08:29, Mathias Bauer wrote:
>> Really, this part of the work is superfluous. IMHO tests that are known
>> to be broken in a particular milestone should be skipped in a CWS based
>> on it also. So if you get a "red" state, yo
Frank Schoenheit, Sun Microsystems Germany wrote:
> Hi Mathias,
>
>> Really, this part of the work is superfluous. IMHO tests that are known
>> to be broken in a particular milestone should be skipped in a CWS based
>> on it also.
>
> Don't think this is a good idea, since a test can be broken i
On 09/23/09 11:17, Frank Schoenheit, Sun Microsystems Germany wrote:
Hi Stephan,
I think this point is moot. I strongly believe that tests that are
regularly run on all CWS must also be run on the MWS, and the MWS must
not be declared ready until all those test succeed.
I believe that, to
Hi Helge,
Helge Delfs a écrit :
Hi Sophie,
On 09/21/09 20:15, Sophie wrote:
- No documentation on the interaction between EIS and QUASTe (or I
didn't find it and yes I can write it by myself ;). There is still one
button that I don't understand in QUASTe that sound to have an impact on
EIS. Als
Hi Mathias, all,
Mathias Bauer a écrit :
Hi Sophie,
thank you for your comments. I'm glad to get feedback from "non code
hackers" also as I'm hoping to make life easier for them also.
Thanks :)
I will add your points to my list. Let me give some immediate answers to
some of your points. I wi
Hi Stephan,
> I think this point is moot. I strongly believe that tests that are
> regularly run on all CWS must also be run on the MWS, and the MWS must
> not be declared ready until all those test succeed.
I believe that, too, but it's theory only. Pretty similar to the theory
that of cour
Hi Mathias,
Mathias Bauer schrieb:
...
Currently the way how localizations get into OOo is very inefficient. At
some point in time a "deadline" is reached and a whole bunch of
localizable content is exported from the source tree and handed over.
Localizers do their work, send it back and have t
Hi Sophie,
On 09/21/09 20:15, Sophie wrote:
> - No documentation on the interaction between EIS and QUASTe (or I
> didn't find it and yes I can write it by myself ;). There is still one
> button that I don't understand in QUASTe that sound to have an impact on
> EIS. Also I'm not sure that what yo
On Sep 23, 2009, at 8:45 AM, Frank Schoenheit, Sun Microsystems
Germany wrote:
Hi Mathias,
Really, this part of the work is superfluous. IMHO tests that are
known
to be broken in a particular milestone should be skipped in a CWS
based
on it also.
Don't think this is a good idea, since a
Hi,
On 09/23/09 08:29, Mathias Bauer wrote:
> Really, this part of the work is superfluous. IMHO tests that are known
> to be broken in a particular milestone should be skipped in a CWS based
> on it also. So if you get a "red" state, you know that something is
> wrong without the necessity to bro
Hi Mathias,
> Really, this part of the work is superfluous. IMHO tests that are known
> to be broken in a particular milestone should be skipped in a CWS based
> on it also.
Don't think this is a good idea, since a test can be broken in different
ways. For instance, if your test checks 10 aspects
Hi Sophie,
thank you for your comments. I'm glad to get feedback from "non code
hackers" also as I'm hoping to make life easier for them also.
I will add your points to my list. Let me give some immediate answers to
some of your points. I will come back if I can say to one of the other
points I h
On Mon, 2009-09-21 at 20:15 +0200, Sophie wrote:
> - Not enough bots or optimized builds bots to have more capacity for
> building install sets.
This was particularly miserable coming up to the feature freeze. I think
there were 80+ hour waiting times on builds on the solitary windows
bot :-(
>
Sophie wrote:
Hi Mathias, all,
Hi Sophie,
[...snip...]
Also I'm not sure that what you (Sun) see is what I (community)
see, we do not have access to the same interfaces.
Well basically the interfaces are the same where possible with only a
few exceptions.
In EIS only the descriptio
Hi Mathias, all,
I'm following your blog post on Gullfoss here. Thanks for this post.
Some feedback from my point of view, dealing with localization and a
very little experience as CWS QA Rep.
Concerning the last, I've already reported the difficulty to get the
builds when so many are enqueu
18 matches
Mail list logo
