TDF Community Blog

The Document Foundation announces LibreOffice 6.0.2

2018-03-01

Berlin, March 1st, 2018 – The Document Foundation (TDF) announces LibreOffice 6.0.2, the second minor release of the recently announced LibreOffice 6 family in just over a month, with around 50 bug and regression fixes. All LibreOffice users are invited to update either to LibreOffice 6.0.2 or to LibreOffice 5.4.5 to solve potential security-related issues.

TDF suggests to conservative users and enterprises to deploy LibreOffice with the backing of certified developers, migrators and trainers (an updated list is available at: https://www.libreoffice.org/get-help/professional-support/). This is extremely important for the growth of the LibreOffice ecosystem.

Technical details about LibreOffice 6.0.2 bug and regression fixes are available in the change log: https://wiki.documentfoundation.org/Releases/6.0.2/RC1 (fixed in RC1).

Download LibreOffice

LibreOffice 6.0.2 is immediately available for download at the following link: https://www.libreoffice.org/download/download/.

LibreOffice users, free software advocates and community members can support The Document Foundation with a donation at https://www.libreoffice.org/donate/. Donations help TDF to maintain its infrastructure, share knowledge, and fund the activities of local communities, such as the event in Surabaya, Indonesia, on March 23/25 (http://libreoffice.id) or the hackfest in Hamburg, Germany, on April 6/8 (https://wiki.documentfoundation.org/Hackfest/Hamburg2018).

Several companies sitting in TDF’s Advisory Board (https://www.documentfoundation.org/governance/advisory-board/) provide either value-added LTS versions of LibreOffice or consultancy services for migrations and training, based on best practices distilled by The Document Foundation.

Friday Community #6

2018-02-23

Bjoern Michaelsen has just announced the LibreOffice Hackfest Hamburg 2018 on April 7th and 8th, which will be the first of The New Generation. Details about the LibreOffice Hackfest Hamburg 2018 are kept on the TDF wiki page and will be continuously updated. If you are interested in joining the event please start adding your name there (especially if you are looking for TDF travel and accommodation sponsorship).

The German LibreOffice community will join the Hackfest in Hamburg, to discuss non-coding topics like localization, documentation, quality assurance and marketing in the German context. This represents a very good opportunity to meet those active in German-speaking countries, and plan and coordinate how to push the project, the product and the brand in the German context.

The LibreOffice Hackfest Hamburg 2018 will be hosted by Freiheit Technologies.

LibreOffice 6.0: Exploring the QA statistics

2018-02-20

By Xisco Faulí, Quality Assurance (QA) engineer

LibreOffice 6.0 was released on January 31 and this is what happened during its development in LibreOffice’s Bugzilla, which started when the 5.4 branch was branched off from master on May 18 2017.

Note: This blog post has been created based on bugs in Bugzilla that have the whiteboard ‘target:6.0.0’, which means a commit for that bug is included in the release. Other commits referring to other bug trackers (ofz, coverity, rhbz, bnc, etc…) are not covered here, as well as others commits not having a reference to our bug tracker (ie refactoring commits).

In LibreOffice 6.0, a total number of 926 bugs and 88 enhancements were worked on, of which 747 were reported during 2017 (73%), and 267 (27%) between October 2010 and December 2016. July 2017 and August 2017 were the months with more reports, 104 and 108 respectively.

284 reports are related to Writer, 175 to Calc, 134 to LibreOffice in general and 112 to Impress.

This is all thanks to 382 users who reported them.

TOP 10 Reporters

Xisco Faulí ( 74 )

Yousuf Philips (jay) ( 69 )

Telesto ( 59 )

Tamás Zolnai ( 44 )

Aron Budea ( 38 )

Gabor Kelemen ( 26 )

Regina Henschel ( 23 )

Samuel Mehrbrodt (CIB) ( 22 )

Mike Kaganski ( 18 )

Olivier Hallot ( 17 )

Once a report has been created in Bugzilla, a third person needs to jump in, triage and confirm it in order to set it to NEW. This is a very important step as it helps the QA Team to deal with the hundreds of bug reports we receive every week.

Doing it in a short period of time after the bugs are reported guarantees those with more priority get fixed more quickly.

67% of the reports were confirmed within the first day, 84% within the first week and 93% within the first month.

Comparing when the reports were created and when they were confirmed gives a similar chart.

This is all thanks to 113 users who confirmed them.

Top 10 Confirmers

Xisco Faulí ( 225 )

Buovjaga ( 92 )

Yousuf Philips (jay) ( 48 )

Aron Budea ( 42 )

Julien Nabet ( 38 )

raal ( 37 )

Tamás Zolnai ( 28 )

Heiko Tietze ( 28 )

Alex Thurgood ( 25 )

V Stuart Foote ( 23 )

Finally, once the reports have been confirmed and triaged, the developers need to investigate and fix them. Sometimes, it can be trivial fix that takes a few minutes to get fixed – sometimes it takes several man days.

10% of the reports got fixed within one day, 51% within one month and 80% within one year.

Taking a closer look at the period between 2017-05-18 and the final release, 111 bugs were fixed in average a month, being August 2017, September 2017 and October 2017 the highest, with 147, 147 and 139 reports fixed respectively.

This is all thanks to 100 developers who fixed them.

Top 10 fixers

Caolán McNamara ( 105 )

Tamás Zolnai ( 57 )

Julien Nabet ( 48 )

Eike Rathke ( 46 )

Miklos Vajna ( 43 )

Michael Stahl ( 41 )

Adolfo Jayme ( 41 )

Yousuf Philips (jay) ( 39 )

Justin L ( 31 )

Heiko Tietze ( 28 )

For more QA statistics, please watch my recent talk at FOSDEM 2018:
https://fosdem.org/2018/schedule/event/ode_overview/

Join in, and help our QA community to polish future LibreOffice releases! We’re a friendly and growing project, and there are many ways to get involved: https://wiki.documentfoundation.org/QA/GetInvolved

Making Macro Programming a Breeze: The BASIC & API Reference Cards

2018-02-192018-02-23

Update: Reference card for runtime library is now available.

One of the recurring issue when using LibreOffice as a replacement of other office applications is the migration of macros to the LibreOffice BASIC dialect and objects. While the LibreOffice BASIC programming language is almost standard, the objects inside a document have different names, methods and properties, and a rework on the macro is necessary in most cases to make it operational again, when imported from other suites.

(more…)

Sunday Marketing #6

2018-02-19

Last week, we have published the crash report chart just two days after the announcement of LibreOffice 6.0.1, to show the impact of the new version on the issues reported by Windows users.

Ten days after the announcement the impact is even more visible, and the chart on the left shows that the situation is now under control.

The trend shows how important is for LibreOffice users to quickly update to the last available version to reduce the number of potential issues.

The Document Foundation 6th Anniversary

2018-02-17

The Document Foundation was incorporated in Berlin on February 17, 2012. Today is the 6th anniversary, and all TDF Members around the world are celebrating another year of outstanding achievements. The last one has been the successful announcement of LibreOffice 6, which represents the combined effort of hundreds of people around the world, involved in development, localization, quality assurance, documentation and marketing. To summarize their activity, we have represented the building process of LibreOffice 6 visual image, from the empty sheet to the final result.

TDF Community Blog

Recent Posts

LibreOffice for Education: Regaining Digital Sovereignty

How donations helped the LibreOffice project and community in 2025

UPDATED Request to the European Commission to adhere to its own guidances

Further Update about Font Replacement

ODF is just the first of the advantages of LibreOffice

The Document Foundation Releases LibreOffice 26.2.1 with Contributions from Community and Ecosystem Partners