Date: prev next · Thread: first prev next last


Hi *,

for the upcoming new version 5.3.0, the builds for beta2 are now
available on pre-releases.

It is in dev-configuration, meaning it won't replace your stable
installation of LibreOffice and can both be used and installed at the
same time as LibreOffice 5.2.3 for example.

5.3.0 is scheduled to be released beginning of February

While the build is made available in all supported languages and 5.3.0
beta1 did mark feature freeze, string freeze did not happen yet and
due to a problem with the update of translation templates,
translations may still be
incomplete.

See

https://wiki.documentfoundation.org/ReleasePlan/5.3#5.3.0_release

for the complete schedule.

Grab the builds from here here:

 http://dev-builds.libreoffice.org/pre-releases/

The list of fixed bugs relative to 5.3.0 Beta1 is here:

http://dev-builds.libreoffice.org/pre-releases/src/bugs-libreoffice-5-3-release-5.3.0.0.beta2.log

So playing with the areas touched there also greatly appreciated  -
and validation that those bugs are really fixed.

Thanks a lot for your help,
Christian

-- 
To unsubscribe e-mail to: early-testing-announce+unsubscribe@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
List archive: http://listarchives.documentfoundation.org/www/early-testing-announce/
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.