LibreOffice 3.3.1 Release Candidate available

The Document Foundation is happy to announce the release candidate of LibreOffice 3.3.1. This release candidate is the first in a series of frequent bugfix releases on top of our LibreOffice 3.3 product. Please be aware that LibreOffice 3.3.1 RC1 is not yet ready for production use, you should continue to use LibreOffice for that.

The Release Candidate 1 is available for Windows, Linux and Mac OS X from our QA builds download page at http://www.libreoffice.org/get-involved/qa-testers/download-qa-builds

More details can be found in the announcement.

Written by:

View All Posts
Follow Me :

13 thoughts on “LibreOffice 3.3.1 Release Candidate available

  1. It seems that LibreOffice is moving very fast. Well done! Is there a place for requests for new features. I haven’t found it yet.

  2. Really well done on this. I wasn’t expecting an RC package for 3.3.1 yet. But, I notice that the deb X86 packages are not available. Any idea when they will be ready for download?

    1. No sooner do I ask the question than the x86 debs appear. For a community that sprang into being only a few months ago this is really impressive.

  3. Can you please use the free identi.ca StatusNet instead or in conjunction with your twitter feeds? Thank you for respecting freedom! peath

  4. Hi I would like to know when the final version of LibreOffice 3.3.1 RC1 since I have it installed and it’s going very well, but as I read some news would be talking to the 3.3.1 final on 14 February, someone Sabai tell me if it will be soon.
    Thanks

  5. LO 3.3 looks good, but it seems very slow (Win 7 pro 32bit, 3GB). How can I increase performance / speed (without hardware modifications)?
    Thx,
    G.

  6. Congrats! Indeed LO is running VERY fast on Linux (Ubuntu Lucid 28.6.32.28)
    Seems bug I posted (FreeDesktop Bugzilla – Bug 33915) has been resolved. Go on like this and LO will be the best Office-Suite in galaxy.

  7. Do you still continue to rely on Oracle-Java or longer for this version and depend only on OpenJDK, because Oracle could be that the idea of changing the license to Java and start harass or sue or something to the project?

Comments are closed.