Am 11/23/2012 09:39 AM, schrieb Jürgen Schmidt:
Hi,
we all know that the number of volunteers helping with translation is
growing and we would like to make new languages as soon as possible
available. This is important for two reason, first to make AOO available
in further languages to reach more users. Second to show our volunteers
that their work is appreciated and become integrated as soon as
possible. We don't have a well defined process for doing it at moment
but we will find a working way that will be ok for all of us. And we can
improve it over time when see demand for changes or improvements, means
we don't have to find a 100% perfect solution from the beginning.
Yes, let's start with this. Thanks for your proposal. I've some
additional comments inline.
The most important part is how we do the naming of the different parts
of such a release.
I see two different scenarios:
1. Only new languages, no bugfixes, no other code changes
We add the new languages on top of the existing AOO34 branch, build the
office with the new languages and release the new languages as
convenience binary packages.
Please make sure to build not only langpacks but also full install
builds. Otherwise the 1-click-download doesn't work for these new languages.
And they have to contain the same version number than the old files.
Otherwise the download won't work, too. The DL scripts uses a single
version number for all files.
> We also build a new src release package and
add the revision number in the name to identify a respin of the orginal
3.4.1.
For example: aoo-3.4.1-rev1372282-src.tar.bz2
This new src release becomes the default for 3.4.1 because it is a
respin only (no functional changes)
The revision number is part of the about dialog as well and it is
possible to identify the respin.
I had a timpestamp in mind but the SVN rev. is much better.
2. New languages + bug-fixes or security fixes
The micro number will be increased and we do a normal release cycle.
The src release will contain the revision number in future always.
IMHO the src file should *always* contain the rev as an unique reference.
Concrete proposal for 3.4.1 and new languages:
1. set a deadline for new translations, for exmaple December 31, 2012
2. integrate the new languages and provide the builds until January 10, 2013
3. test and verify the new language builds asap
4. release the new languages at the end of January
Sounds good to me.
Just to make sure to avoid any misunderstandings:
+1 for scenario 1.
Why a deadline until December:
The reason is quite simply, we have 22 languages with an UI coverage of
more than 95% (ok Turkish 93%). My plan is to prepare a blog entry and
call again for volunteers for these languages where the effort is
moderate. My hope is that we can integrate a few of the important ones.
UI coverage with more than 93%
==============================
100%: Danish
98%: Korean, Polish, Asturian, Uighur, Icelandic, Indonesian, Welsh,
Catalan, Bulgarian, Latvian
97%: Greek, Basque
96%: English (South Africa)
95%: Portuguese, Swedish, Marathi, Kannada, Gujarati, Irish, Oriya
93%: Turkish
Good. Many more "nearly-perfect-languages" to come. :-)
Marcus
