Hi all,
I'd like to add some comments...
Providing localized builds on the one hand and providing a release
candidate and stable localized builds is something different from my
point of view.
Full localized builds (l10n snapshot builds) can be uploaded to one
single FTP server. Such builds do not necessarily need a mirror network
(~120 servers that host the files worldwide). One example is the l10n
snapshot build of OOO310_m5 that has been uploaded by Ivo Hinkelmann.
Such a build (> 100 GB) would never fit onto the extended mirror network.
Release candidate builds and stable localized builds need to be mirrored
because such builds get downloaded millions of times. Since version 3.0
there were more than 50000000 downloads. Unfortunately the mirror
network is in my opinion too small.
The "mirror network" includes three different volumes:
The regular mirror network (~30 GB) contains: "stable" en-US builds +
source tarballs + a part of "localized" builds
The extended mirror network (originally planned to have ~100 GB but
nowerdays a bit larger) contains: release candidate builds, developer
snapshots, ISO files and those localized builds which do not fit into
the regular mirror network (currently about 10 GB). There are some more
files that do need to be mirrored via this mirror network.
The archive mirror network contains mostly all content that has been
removed from the regular mirror network. Localized builds that were
available and that have been removed from the extended mirror network
need to be archived manually.
Maybe it would help if we can reduce the number of files by providing
wJRE builds only instead of providing builds with JRE and builds
without. Builds with a JRE contain a setup application.
Kind regards, Joost
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
