Brian Vincent wrote:
I didn't add in a formal method for doing this, but what we have right
now is pretty much two different scenarios:
1) winrash client has never downloaded a test.
- so we send them every winetest we have
2) winrash client has downloaded a winetest
- we send them only the mo
As it was written in the Book of Jakob Eriksson <[EMAIL PROTECTED]>:
> I don't understand any of this and it worries me.
It's ok, really ;)
> Do you mean separate tests, like "kernel32_crosstest.exe", or do you mean
> "winetest.exe"?
The two examples I listed are the only two things we support r
As it was written in the Book of "Dimitrie O. Paun" <[EMAIL PROTECTED]>:
> What we need to support:
> -- multiple publishers
> -- multiple files for the same build for each publisher
> -- various distribution policies
Okay, this is mostly done. Please note the following changes that
must b
And the thrist and last installment:
SERVING (Brian)
---
What we need to support:
-- multiple publishers
-- multiple files for the same build for each publisher
-- various distribution policies
What we need to do:
-- maintain a pool of releases as described in my
previ
