From The Document Foundation Wiki


    Quick Start :

    1. Download: here!
    2. Test what you want
    3. Find a bug? Mention it on QA/IRC or file a bug!

    It's as simple as that -- your help is greatly appreciated!


    Our community is preparing for the release of LibreOffice 5.0.0 (previously denominated 4.5). We've added many new features and fixed loads of bugs (see below...), and we want to make sure that the new version is well tested. You can help to make this release a great one! Be aware however that the translation for this version may not be over and is not yet integrated.

    On the 19th, 20th and 21st of June we will have an international bug-hunting session, testing the first RC of LibreOffice 5.0.0. Please join us! :-)

    How to join

    Linux (64-bit)

    Note that it will replace your actual installation, this is a release candidate version. Save all you customisations (profile, etc) to make sure they won't be corrupted if there is issues

    Ubuntu PPA

    [ RC1 packages will appear shortly ]

    For those on *buntu platforms, we also have a PPA with pre-releases:

    That PPA currently has rough 5.0.0~beta3 packages including kde support for Ubuntu 15.10 (vivid), Ubuntu 14.04 LTS (trusty) and Ubuntu 12.04 LTS (precise).

    When: June 19, 20 and 21

    Feel free to join us at any point during these three days.

    • #Mentors will be available from 08:00 UTC to 22:00 UTC on those dates.

    If you can't join us during this session, you're always welcome to help us hunt for bugs on other days. The builds of this particular RC1 (LibreOffice 5.0.0. RC1) will be available until July 7th ;-)

    What to test

    We aim at:

    • Doing as much testing on the 5.0.0 as possible
    • Triaging all already filed issues, so that it's as clear as possible for the developers to step in!

    There are always more ways to test: do your regular tasks, structured tests, or playing with the new features..

    Choose what suits best for you :-) All testing is great and important, and the more we are, the more chance we have to hunt a bug!

    So take one of those:

    SDK Examples

    We don't need to test our included SDK examples during every BH Sessions, but at least once before a major release we should make sure that the extensions still compile and work as expected.

    • Code:;a=summary
    • Compile and test
    • The contents of the repository should be self-documented (including how to build, etc. If they aren't, then that's a bug (per Bjoern))
    • Any updates/fixes to the documentation and examples should go into the git repo. Per Bjoern, "the stuff should work for someone without IRC, so whatever is missing should be in the repository READMEs, not in some IRC log"

    Found a bug?

    At first, make sure it isn't already reported by searching in our bug database. If it isn't reported yet, you can add it to our bug database using our BSA, which is a simple layout to report bugs. If you are more confident with Bugzilla, you can report your bug using the Bugzilla interface. When you want to discuss first, use chat or mail, fast and direct.


    If there is a bug that you want to pin point as clear as possible, then bibisect (explained by Bjoern Michaelsen) will be a great tool for you (for advanced testers)!

    Get a little support

    Other users and testers are at IRC and the mailing list to help with any question. Don't be shy, don't hesitate to ask!

    More info on Moztrap, to work with our test cases, is here

    If you have an idea for a test case, feel welcome to post this at our QA mailing list


    Who's available to manage the #libreoffice-qa IRC:// channel? It would be great to have a couple of people providing coverage most of the day...

    • add your nickname