Hi,
Le 26 juin 08 à 16:55, Joost Andrae a écrit :
Hello Charles,
as far as I can remember we have the follwing deal since some time
now:
* If UI has more that 80% translation coverage then a language pack
is provided by Sun.
* If additionally more than 80% help content coverage is available
then Sun provides full installation sets.
* If a localization is not maintained for several releases then Sun
stops providing builds for this localization.
Regarding the delivery process there are two more things to mention:
* QA build approvals are registered at qatrack.services.openoffice.org
* distribution requests are to be sent as issues.
Example:
http://www.openoffice.org/issues/show_bug.cgi?id=90764
http://qatrack.services.openoffice.org/view_status.php?version=2.4.1&language%5B%5D=fr&available=&uri=&view=detailed
Do you have any commments or do you prefer other criteria ?
What you are saying has some far-reaching consequences: are you
implying that Sun is going to release builds for every language
already covered ?
I remember the criteria for the language packs, but I have to admit
that I completely forgot the one about the 80% translation of the help
content allowing for Sun providing the installation sets.
I actually think this is a good thing although it highlights something
else: many localization team do not/cannot/don't have the resources to
fully or adequately localize the help content. That's not real news
but it shows we have a lasting pattern of teams not localizing that
part and the situation does not seem to improve (we obviously need
more metric, I'll check the QA Track).
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.
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)
- notification of the new, localized version which ultimately rests on
the localized build maintainer's ability to launch the notification
procedure.
I think that's what the issue here. Do you think we can change it?
Best,
Charles.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
