>> The 
>> reason is that we want to get an overview over
the qa-progres, and 
>> distribute the RC over the mirror
network 
> 
> RC builds are already distributed over a
limited section of the 
> mirror network that is called the
extended mirror network. For QA 
> purposes, often a single server
is enough to distribute the builds 
> for one language or OS. The
new chart CWS had a high demand for a CWS 
> being tested and was
on one server, which coped fine. The Aqua port 
> on Mac OS X of
ooo however requires both the mirror network and 
> BitTorrent to
distribute due to the high demand. 

Hello, thanks for the
answer

sry, I think perhaps that I have misunderstood the
RC-label
with RC I mean the final build that is going to be released
for distribution

>> The platforms that we 
>>
currently tests are: linux intel (deb+rpm), windows and hopefully soon 
>> mac 
> 
> All X11 Mac builds are currently
produced by maho and placed on the 
> FTP server at 
>
ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/ 
yes,
but there are builds on pavels server as well, are there any difference

>> we also would like to ask if it is possible to distribute

>> our own iso (boundled windows-installer, java and
documentation) 
>> over the 
>> mirror network ...
suppose that this should go via the qatrack as well 
> 
>
There will be no problem adding them to BitTorrent for distribution. 
> It might be an issue for adding them to the full mirror network.

well, my impression is that the common user in denmark isn´t
familiar with torrent-downloads
but if this is the option, thay have
to learn it
or does "might be an issue" mean that it is
something we need to talk about

and just another question. I
have got the impression that it is a requirement to have an approved entry
on qatrack before you request new builds to be published on the mirror
network
am I wrong?

I appreciate any comments

regards 
thomas roswall
danish qa-coordinator


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to