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
