Home Home > 2011 > 03 > 01 > LibreOffice 3.3.1 bugfix release available for openSUSE
Sign up | Login

Deprecation notice: openSUSE Lizards user blog platform is deprecated, and will remain read only for the time being. Learn more...

LibreOffice 3.3.1 bugfix release available for openSUSE

March 1st, 2011 by

I’m happy to announce LibreOffice 3.3.1 bugfix release for openSUSE. The packages are available in the Build Service LibreOffice:Stable project. They fix various crashers, usability and translation problems, see the libreoffice- release news for more details. See also some notes about openSUSE LibreOffice build.

The openSUSE LO team hopes that you will be happy with this release. Though, any software contains bugs and we kindly ask you to report bugs. It will help us to fix them in the future releases.

Other information and plans:

This version will be in openSUSE-11.4 out of box. We are going to prepare official maintenance update for openSUSE-11.2 and 11.3.

There are already several fixes for the LO-3.3.2 bugfix release. You might expect 3.3.2-rc1 in the “LibreOffice:Unstable” repositories by the end of the following week.

Most developers are already concentrated on LO-3.4 release. I hope that the first beta packages will be ready in the beginning of April.

Both comments and pings are currently closed.

2 Responses to “LibreOffice 3.3.1 bugfix release available for openSUSE”

  1. Dave Griffiths

    Hi Petr,

    The document at http://cgit.freedesktop.org/libreoffice/build/plain/NEWS?id=libreoffice- suggests that this is libreoffice- (3.3.1rc2)

    I thought the STABLE repository was supposed to contain 3.3.1 final, as released on 23 Feb? Am I misunderstanding something here?



    • Petr Mladek

      Hi Dave,

      I am sorry for the late reply. It is a pity that the system does not send any mail notifications about new comments.

      Please, look at http://www.libreoffice.org/download/release-notes/. It already points to 3.3.2 release. Though, it states that the final release is bit-for-bit identical to the 3.3.2 Release Candidate 2. The same situation was also with 3.3.1 release.

      The idea behind this is that the LO community does not want to release the final build without public testing. It means that it produces release candidates and when there is no blocker found, the last release candidate is marked as final.