Hi,
there have been created the tag libreoffice-4.0.4.2, 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 4.0.4.1.
Now, you might switch your current 4-0 source tree to it using:
./g fetch --tags
./g checkout -b tag-libreoffice-4.0.4.2 libreoffice-4.0.4.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#4.0_release
and release criteria at http://wiki.documentfoundation.org/Release_Criteria
Best Regards,
Petr
+ FILEOPEN: Incorrect displaying attached VSD document (fdo#64797) [Fridrich Štrba]
fdo#64797 FILEOPEN: Incorrect displaying attached VSD document [Fridrich Štrba]
+ common
+ version 4.0.4.2, tag libreoffice-4.0.4.2 [Petr Mladek]
+ core
+ accept even more corrupted zip documents as long as we can read them [Fridrich Štrba]
+ fix crash with fdo60063-1.docx [Fridrich Štrba]
+ revert "fix Set TEXT_LAYOUT_BIDI_STRONG flag." (fdo#60533) [Petr Mladek]
+ transform the clipping polygon before using it [Fridrich Štrba]
+ updated core [Andras Timar]
+ uploading libvisio-0.0.28 fixing regression (fdo#64797) [Fridrich Štrba]
+ translations
+ update translations for LibreOffice 4.0.4 rc2 [Andras Timar]
Context
- [ANNOUNCE] libreoffice-4.0.4.2 tag created · Petr Mladek
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.