Home Home > 2009 > 04 > 21 > OpenOffice_org 3.1 beta5 available
Sign up | Login

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

OpenOffice_org 3.1 beta5 available

April 21st, 2009 by

I’m happy to announce that OpenOffice.org 3.1 beta5 packages are available in the Build Service OpenOffice:org:UNSTABLE project. They include many upstream and Go-oo fixes. Please, look for more details about the openSUSE OOo build on the wiki page.

The packages are beta versions and might include even serious bugs. Therefore they are not intended for data-critical usage. A good practice is to archive any important data before an use, …

We kindly ask any interested beta testers to try the package and report bugs. See also the known blocker bugs below.

This build finally includes the alpha version of OpenXML export filters (DOCX, XLSX, PPTX). There are still many serious bugs, e.g. bnc#496431, bnc#492896. We also added many fixes to the OpenXML import filters. These changes affected also the import and export filters of the old binary file formats (DOC, XLS, PPT). So we kindly ask anyone to try this functionality and report bugs especially in the import and export of the old binary file formats.

Known blocker bugs:

  • Word DOC with the table of connt is read only (bnc#400884)
  • Report builder extension does not work (bnc#496747)
  • Other information and plans:

    I would like to provide beta5 or rc1 build the following week. I expect the final release in the first half of May. We will be slightly delayed after the upstream release.

    Both comments and pings are currently closed.

    4 Responses to “OpenOffice_org 3.1 beta5 available”

    1. smspvdm

      You mean first half of may, I presume?

    2. jake

      …beta5… couple of weeks after OO.org’s rc1 released…
      How lang it take (time) release from openSUSE community?
      I can’t understand – sorry!

      • Petr Mladek

        It is just a naming scheme. Upstream does not use beta versions. It provides just so-called milestone builds. I think that alpha, beta, rc names are more descriptive and more tell about the quality. Release candidate should not contain any known blocker bug. The openSUSE build is delayed by few days after the upstream by definition. The openSUSE beta5 build was based on the upstream 3.1-rc1 sources but I didn’t want to mark it as rc1 because I already know about the other blocker bugs => I used another beta version number in the row for it.

        BTW: The upstream OOo-3.1-rc1 was released 3 weeks ago. They added 30-50 fixes within the last 3 weeks. I think that the name beta was better description.

        Another problem is that the openSUSE build is not based on the pure upstream sources. It is based on the GO-oo sources. There are many changes. The GO-oo developers do their best to be in sync with the upstream schedule but it is not always possible. Upstream often delays releases be several weeks. It is normal that this happen also in the GO-oo project with its additional features and fixes.

        In each case, feel free to help us to deliver the packages on time. The GO-oo developers are still looking for more helping hands. Also I am looking for a co-packager 😉