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


Hi all,

The tag libreoffice-5.2.2.2 (AKA 5.2.2 RC2) has been created on the
libreoffice-5-2-2 branch.
The branch will be used for fine tuning of the 5.2.2 release. (It is
the last scheduled RC)

The following rules apply to the branch:

        + preferably just translation or blocker fixes
        + only cherry-picking from libreoffice-4-2 branch
        + 2 additional reviews needed; 2nd reviewer pushes
        + no regular merges back to anything

The ‘libreoffice-5-2' branch is still active and will be used for the
5.2.3 release. Please read more at
       http://wiki.documentfoundation.org/ReleasePlan/5.2#5.2.2_release
       http://wiki.documentfoundation.org/Development/Branches
       http://wiki.documentfoundation.org/Release_Criteria

To checkout the tag, use

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

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

Attached is the list of changes against 5.2.2 RC2

Happy hacking,
Jan I

Attachment: commits-(HEAD-release-libreoffice-5.2.2.2.log
Description: Binary data

Attachment: bugs-changelog-(HEAD-release-libreoffice-5.2.2.2.log
Description: Binary data

Attachment: bugs-(HEAD-release-libreoffice-5.2.2.2.log
Description: Binary data


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.