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


2012/10/23 Petr Mladek <pmladek@suse.cz>

Hi,

there have been created the libreoffice-3.6.3.2 tag (aka rc2)[*]. The
corresponding official builds will be available within next few days.
It will be used as final if no blocker is found.

See the attached list of changes against 3.6.3.1.

Now, you might switch your current 3-6 source tree to it using:

./g fetch --tags
./g checkout -b tag-libreoffice-3.6.3.2 libreoffice-3.6.3.2

Linux distro packages might find source tarballs at
http://dev-builds.libreoffice.org/pre-releases/src/
They will be available from the official page together with the builds.


See also the schedule at
http://wiki.documentfoundation.org/ReleasePlan#3.6_release
and release criteria at
http://wiki.documentfoundation.org/Release_Criteria


Best Regards,
Petr

_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Hi, at all

Few days ago I have sent a important bug for integration. I know that here,
in lists is not the way for manage it, but...

New spellchecker fo galician
https://bugs.freedesktop.org/show_bug.cgi?id=56130

There was not response until today. Can somebody take care as it's a
important enhancement for us?

Cheers,

Antón





-- 
Antón Méixome - Galician Native Lang Coordination
Galician community LibO & AOO

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.