Second Bug Hunting Session for LibreOffice 5.4

LibreOffice 5.4 will be announced at the end of July 2017, with a large number of new features which are summarized on the release notes page: In order to find, report and triage bugs, the QA team is organizing the second bug hunting session on Friday, June 09, 2017. Tests will be performed on the second Beta version of LibreOffice 5.4, which will be available on the pre-releases server ( a few days before the event. Builds will be available for Linux (DEB and RPM), MacOS and Windows, and will run in parallel with the production version.

Mentors will be available on June 09, 2017, from 8AM UTC to 10PM UTC on FreeNode #libreoffice-qa channel (connect via web chat). Of course, hunting bugs will be possible also on other days, as the builds of this particular Beta release (LibreOffice 5.4.0 Beta2) will be available until the third week of June.

During the day there will be two dedicated sessions: the first to chase bugs on the main LibreOffice modules between 3PM UTC and 5PM UTC, and the second to test a set of the top 7 features between 5PM UTC and 7PM UTC. All details of the second bug hunting session are available on the specific wiki page.

During the dedicated sessions, we will concentrate all efforts to chase and reproduce the bugs, in order to confirm and file them in a more comprehensive way. Of course, the more comprehensive will be the bug report, the easier will be for the developers to solve the bugs in time for the final release.

Besides, there will also be manual tests to be executed in TestLink, our new platform for manual tests. More information about TestLink here.

As a new feature this time, we will reward every participant who reports a bug found [*] in LibreOffice 5.4 Beta2 with a shiny ‘Proud Contributor’ sticker:

[*] In order to claim the sticker the bug needs to be reproducible in LibreOffice 5.4 Beta2 and it needs to be a not-yet-reported regression introduced in LibreOffice 5.4, a crash or a bug in a new feature introduced in LibreOffice 5.4. The bug’s description must have the detailed steps to reproduce the problem and the affected document if needed.

No Responses