Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


Hi Andrea, all,
On 05/12/2010 20:39, Andrea Pescetti wrote:
On 26/11/2010 Petr Mladek wrote:
http://wiki.documentfoundation.org/Release_Criteria
Feel free to update it or propose improvements. Especially, I am not
sure about bugs in localizations.

So a major change with respect to the OpenOffice.org release process
would be that no explicit approval is needed for localized versions.

Imho, this should still be needed. Manuals tests are currently developed on the wiki and they should be run on each language for approval of the build to be elected as stable.

This is probably related to the multi-language build model, where you
don't want to wait for 20 or so explicit approvals in order to release
the English version, but still distributing possibly untested software
does not seem very good to me: I did see cases at OpenOffice.org where
only one localized version would not start, or would have blocking
issues.

I agree and this is why the non tested build were left on RC state. We should not change this or we will miss some quality.

If you need very recent examples, in the OOo 3.3 release cycle at least
two localization-specific stoppers were found and fixed upstream in
OpenOffice.org and thus ported to LibreOffice too:
http://qa.openoffice.org/issues/show_bug.cgi?id=115232 [IT only]
http://qa.openoffice.org/issues/show_bug.cgi?id=115774 [FR only]

Kind regards
Sophie

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.