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


Hi,

please note that the commit deadline for 3.6.2-rc1 is on Monday, September 10,
2012.

Andras, l10n teams, there as few more string to fix the nasty date-recognitions bugs[*].
Please, try to have them localized until Sep 23, 2012 when is the deadline for rc2.

The tag and branch libreoffice-3-6-1 is going to be created the day after.
Only commits with 3 reviewers will be allowed for that branch.

See also
http://wiki.documentfoundation.org/ReleasePlan#3.6_release
http://wiki.documentfoundation.org/Release_Criteria
http://wiki.documentfoundation.org/Development/Branches


Best Regards,
Petr

PS: Please, help with reviewing the pending commits.


[*] It is the commit
http://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-3-6&id=cfbfa26deb2776e5c07463e59517eaf68c1d5d6d
that solved bugs:
        + https://bugs.freedesktop.org/show_bug.cgi?id=52240
        + https://bugs.freedesktop.org/show_bug.cgi?id=52137
        + https://bugs.freedesktop.org/show_bug.cgi?id=52288
and many duplicates.



-- 
Unsubscribe instructions: E-mail to l10n+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

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.