-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andrea Pescetti wrote:
> Comparing http://www.openoffice.org/download/other.html and
> https://translate.apache.org/projects/aoo40/ I see that we have: -
> Two unreleased languages that are now 100% translated (Bulgarian
> and Danish) - One language with only about 1000 words left and
> activity in the last week (Norwegian Bokmal) - Three languages with
> about 4000 words left and activity in the last week (Thai, Uighur,
> Hebrew; Indonesian and Icelandic are in the same group, but less
> active)
> 
> Would it make sense to schedule a "language update" 4.0.1 release
> for late November? I mean something like: announce a translation
> deadline on the l10n list, produce SDF files for the languages that
> reach 100% (which of course already include Bulgarian and Danish,
> and hopefully some of the other languages listed above), building
> only those languages and releasing an updated source package and
> binaries for those languages.
> 
Yes I believe that it would make sense and would add to our reputation
for actively supporting native languages.
It would make more snse
> So this would work like we did for 3.4.1 when we added new
> languages. Why not call it 4.0.2? Well, we already discussed it,
> but the main reasons would be: for the languages already released
> in 4.0.1, 4.0.2 would be identical (example: 4.0.1 in French would
> be identical to 4.0.2 in French) since all commits in the meantime
> have been done to trunk; a new 4.0.2 release takes a much larger
> effort than a 4.0.1 language update, so it is harder to find
> volunteers and this is worth doing only if we have some important
> bugfixes for 4.0.1 to include (and I don't see any at the moment).
> 
It would make more sense for it to be 4.0.1 unless there were critical
bug fixes that would justify a 4.0.2. The only potential glitch that I
see is handling the release notes. I have a couple of ideas that I
will lay out in a separate thread if we decide to go ahead with a
language only release.

Regards
Keith
> Regards, Andrea.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSdpViAAoJEH0fu5UhGmBCBUEIAJsZ4L1VznYd3eM66QdCQfi3
fN/v+488QzGVjWDqSTL77S0AXI/+AdnWpi8uTTiS86VRlVU+JpVxSLXyiOp7XqZH
llF/4gqYtZgCat7GqLrN7b377H0mY2VkCGfMy1W/1CeypDYtimvSA29Uaan0TQhU
B+kssxfXZeRGg+6EL5odHKvFaYEN+q/01GFTvK7+TFaW7x5Z1rkK5MoVn07TeQUC
/myU1l+m9UJ3TtA6MRKai+tqCLkUzUnFLgWoSh+oo1l6o6wGd1HYdmwL6adT7Nvg
9KidA6AhJjHSsR9quKqGbaaFHSv5RKNfHvjcVYWNZO9C+Jwva5sywcOFqEz5j7U=
=8n2C
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to