QA Archive

LibreOffice community focus: QA (quality assurance)

With LibreOffice 6.0 due to be released at the end of the month, we’ve been talking to various communities involved in the project. In the last couple of weeks, we’ve chatted with the localisation and documentation teams, and today it’s the turn of QA (quality assurance), which is coordinated by

Coming up on December 22: Bug Hunting Session for LibreOffice 6.0 RC1

2017 is coming to a close, but our community is still busy preparing for the release of LibreOffice 6.0, which is due in late January 2018. Many new features have been added to this version, and to make it as reliable as possible, we want your help!

On December 22

Second Bug Hunting Session for LibreOffice 6.0

After the first Bug Hunting Session for LibreOffice 6.0, which was held on October 20th 2017, we’re glad to announce the Second Bug Hunting Session on November 27th – this time being held on a Monday, for the first time!

LibreOffice 6.0 will be announced at the end of January 2018, and

Coming up on Friday: first Bug Hunting Session for LibreOffice 6.0 Alpha 1

The LibreOffice community has returned from a great conference in Rome (more on that later this week), and we’re now working eagerly on LibreOffice 6.0, which is due to be released at the end of January 2018. This version will include a large number of new features – and those already implemented are

Surpassed the 40,000 closed bugs milestone

As Tommy kindly mentioned on the QA mailing list, this week the LibreOffice project has surpassed the 40,000 resolved bugs milestone – a huge achievement demonstrating the enormous amount of effort the community puts into software quality. If we take a look at the numbers from August 2016 (the month we started

LibreOffice Quality Assurance: six months in statistics (part 2)

This is the second part in our blog series about the LibreOffice QA (quality assurance) community – see here for the first part.

Regressions

During the six month period from 23 November 2016 to 21 May 2017, 553 bugs were identified as regressions by 61 people. This means a feature behaved correctly in the past