17 Dec 2018

Coming up on December 21: Bug Hunting Session for LibreOffice 6.2 RC 1

Posted in LibreOffice, QA By Mike Saunders On December 17, 2018

After the first and second Bug Hunting Sessions of LibreOffice 6.2, which were held on October 22th 2018 and November 19th 2018 respectively, we’re glad to announce the third and final Bug Hunting Session for LibreOffice 6.2 on December 21st. You can see the release notes describing the new features here.

In order to find, report and triage bugs, the tests during the Third Bug Hunting Session will be performed on the first Release Candidate (RC1) version of LibreOffice 6.2, which will be available on the pre-releases server on the day of the event. Builds will be available for Linux (DEB and RPM), macOS and Windows.

Mentors will be available on December 21st 2018, from 7AM UTC to 19PM UTC for questions or help in the IRC channel: #libreoffice-qa and its Telegram bridge. Of course, hunting bugs will be possible also on other days, as the builds of this particular Release Candidate (LibreOffice 6.2.0 RC1) will be available until mid January, 2019. See the release plan.

During the day there will be two dedicated sessions, one about the new KDE5 Integration between 11AM UTC and 13PM UTC and the other about the tabbed NotebookBar from 15PM UTC to 17PM UTC as it is not experimental anymore.

Comments

  1. By Rick

    Have you guys finally fixed the animated GIF’s bug where we can load animated GIF’s and after loading more than say three or four into a presentation the program won’t hang and just fall out of control?

    It seems really big bugs never get fixed but loads of small things get added all the time – yet these are what would be considered quite serious bugs in commercial software. These bugs have been reported for ages in the Bugzilla and yet never get fixed and makes Impress a very underwhelming program to use for serious presentation work.

    • By Mike Saunders

      Hi Rick, LibreOffice is a volunteer-driven, community open source project – bugs only get fixed if people step up to work on them! Nothing happens by magic. Volunteers work really hard to provide you – and everyone else – with a complete office suite, so if you want to see more bugs fixed, you can contribute back, by either helping to fix them, or funding a certified developer to work on them: https://www.documentfoundation.org/gethelp/developers/