Hi Charles,
Without dwelling too much on this, I think that what you describe is good, efficient, but falls behind the point. It would be better if each language could simply have the update notification on and working, regardless of Sun's coverage.
that would be possible if all build providers include that feature at build time. That is not the case. On the other hand the product update service requires manual interaction it does not work like magic.
We have to distinguish two levels of notification (NB: I'm not talking about the automatic, incremental update that we do not have on OOo): - notification of the new version regardless of the localization readiness. That could even be configured automatic update of developers' build (see Firefox)
That should already be the case for en-US developer snapshots. Language packs are not notified (AFAIK).
- notification of the new, localized version which ultimately rests on the localized build maintainer's ability to launch the notification procedure.
Update notification of releases can be done if 1. the build has the update notification feature included/activated 2. the build has been distributed to the mirrors 3. a) the Bouncer links work b) a localized landing page is available eg. http://update.services.openoffice.org/ooo/index_fr.html 4. the build has been tested and approved for distribution
I think that's what the issue here. Do you think we can change it?
If there would be enough disk space on the mirror network I believe Sun could provide a lot of more localizations as full builds and it would be possible to lower the requirements to get a full build.
Kind regards, Joost --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
