Markus Mohrhard

Work on the automatic updater for LibreOffice has progressed and daily builds with the updater are provided already for Windows and Linux. However, the updater will not be available in the 6.0 major release. We will explain how the updater works, which problems have been addressed already and what still needs to be done.

The LibreOffice automatic updater currently under development is based on the Mozilla mar updater code. The integration of the code was started as a GSoC project in 2015 and has seen more work since the end of 2016. Since mid of 2017 daily builds are available that contact the new LibreOffice update server and provide automatic updates. The distributed updates include full updates as well as differential updates depending on the age of the builds.

During the talk we will start by discussing the updater server infrastructure and show how the new code allows to collect a number of metrics that help the whole project. Next, the client side with the integration of the mozilla based mar code will be discussed. This includes the already existing features and an explanation how existing updater builds are already generated. Finally, the challenges that are still ahead will be shortly outlined, including a short demo showing the new MSI update file generation code.

The crash reporter showed that the LibreOffice project has a serious update problem with users using old versions and not updating to newer versions. The talk will present the work on the automatic updater as well as the approach to collect some user statistics to improve the crash reporter.

Based on the Mozilla updater code an automatic updater has been under development for the LibreOffice project for quite some time. Based on the experiences with the crash reporter the need for an automatic updater has been shown to be a serious problem for the project. The talk will show the current approach used in the automatic updater code, open challenges and how this allows to rethink the installation and packaging experience. Based on the prototype server the talk will also show how the server can be used to generate am estimation for active daily users (ADU) and how the information about the number of ADU can be used to enhance other services.

This talk will present a prototype for crash reporting in LibreOffice. The talk will show the client and server components and include a live demo of the Linux client and the server.

This talk will present some of the automated tools that the LibreOffice project is using to improve the quality of the code. This includes coverity where the LibreOffice project managed to reach a nearly perfect defect density score of 0.00 and the import/export crash testing with about 75000 documents.

This talk will present the work to integrate an OpenGL vcl backend.

A short presentation of the tests the Libreoffice team uses to test import and export filters.

The Libreoffice team uses a number of tests for import and export testing. We will present what and how we use different approaches to make Libreoffice better. As a highlight we will present our script that imports around 45000 documents in various formats and exports more than 60000 documents regularly on a server. Additionally we will show some of the in-build file format testing approaches used in the Libreoffice project.

A short overview of the new time based charting feature in Libreoffice.

Libreoffice brings now support for new time based charting. We will present this new feature and show some possible development ideas for the future. Additionally we we show the new 4D real time charting that is possible with this new approach.

This talk will show how to find performance problems in Calc and how to identify the right place to fix it. The main focus of the talk will be around calc but the main ideas can also be used in other parts of Libreoffice. The presentation will show how to use gdb, callgrind, kcachegrind and a bit of understanding of the Calc core makes fixing performance problems easy.

A short introduction to debugging calc import and export filters. The talk will show where to put breakpoints and how to find the right source code file for different filters/features.