Hi,

Florian Effenberger wrote:
Hi Rimas,

Didn't I offer a solution for exactly this problem? Please re-read point
2) above, I just removed the unnecessary example from it.

for sure, it would be a solution, at least for interim time, to host "less-downloaded" languages only on a few selected servers. From what I understand, MirrorBrain can perfectly work with that, checking each mirror's files and only redirecting to those having the file.

I say interim because of course, mid- to long-term, our plan is to grow adoption of OpenOffice.org in those countries, so we hope they need more mirrors soon. :-)

But, I agree, it could be a possible option. For that, we first need to get more detailed download statistics (or collect them centralized) to see which languages are downloaded less than others.

Joost, Stefan, what do you think? Could that be an option we should envision? I agree to Stefan that first checking/reducing the combination of platform, language and JRE is the best approach, but if that doesn't suffice, Rimas idea might be worth thinking of...

Rimas' idea to group builds by geographical region will certainly help
mirrors that would like to carry some (>1) languages but can't carry all
.../localized. This would be achievable already today with some options
to rsync. But this can only show effect with a better tool for download
management.

At the moment we work with 2 (actually 4) sets of data and the
corresponding mirrors - main, extended (plus cws-/l10n-test and the
archive).
I think we should look at the policies talking about mirror usage, QA,
the archive, localized builds and
- invest in the future not in legacy by archiving dated releases/RCs
- keep QAed stable releases for all languages in the main set
- provide builds for l10n-test for all languages and for reasonable
(tbd) platforms
- provide RCs for QA and release for languages with >80% UI translation
and for a reasonable (tbd) platforms
- allow NLC-QA-teams to work on all available platforms for their language

Concrete steps coming to mind are
- review archival guidelines
http://distribution.openoffice.org/mirrors/archive.html
- notify about mirror clean-up and archive dated builds
- define l10n-test platforms
- review l10n build guidelines (sorry, where were the 80% mentioned?)
- define RC platforms
- move .../extended/localized to .../localized
- define a way for QA-teams to request remaining platforms
- adapt the documents / policies to the changes

Gruss
Stefan


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to