This is a feed aggregator that collects what LibreOffice and Document Foundation contributors are writing in their respective blogs.
To have your blog added to this aggregator, please mail the website@global.libreoffice.org mailinglist or file a ticket in Redmine.
Developers and database administrators often operate under a common assumption: unlocking powerful new software features requires significant, time-consuming, and expensive development work. New capabilities frequently sit on the shelf, waiting for the budget and time to rewrite applications to take advantage of them.This assumption, however, doesn't always hold true. Recent versions of the
Digital identity has become an integral part of everyday life. We use it to access work tools and sign documents online, and it is even replacing physical identity cards. However, most discussions on the subject focus on authentication systems, encryption and biometrics, ignoring the formats that actually carry our information.
Berlín, 18 de diciembre de 2025 – LibreOffice 25.8.4, la cuarta actualización menor del paquete de oficina gratuito desarrollado por voluntarios para la productividad personal en entornos de oficina en Windows, macOS y Linux, ya está disponible en la página de descargas. Con LibreOffice 25.2 llegando al final de
Berlin, 18 December 2025 – LibreOffice 25.8.4, the fourth minor update to the free office suite developed by volunteers for personal productivity in office environments on Windows, MacOS and Linux, is now available from the download page. With LibreOffice 25.2 reaching the end of life on 30 November, and the
Zdeněk Crhonek (aka “raal”) from the Czech LibreOffice community writes: The new version of the LibreOffice Draw Guide 25.8 has been translated, and announced on our social media. The team is almost identical, with translations by Petr Kuběj, Zdeněk Crhonek and Radomír Strnad and technical support from Miloš Šrámek. Download
La comunidad hispana de LibreOffice se complace en anunciar la publicación de la Guía de Writer 25.2 en español, un nuevo aporte construido de manera colaborativa y abierta, reflejo del compromiso de quienes participan activamente en el proyecto. LibreOffice Writer es una potente aplicación de procesamiento de textos que admite
At the recent Open Source Conference 2025 in Luxembourg there were two talks about LibreOffice. The first was Lessons learned from 13 years at The Document Foundation and LibreOffice, where Florian Effenberger, Executive Director of the foundation, talks about the legal setup of The Document Foundation and how its statutes
I decided to start the current campaign, with one blog post per week focusing on the different aspects of Open Document Format, to celebrate the 20th anniversary of the standardisation by OASIS, which happened in May 2005. My hope was to raise the interest around ODF, which is the document
LibreOffice 26.2 will be released as final at the beginning of February, 2026 ( Check the Release Plan ). LibreOffice 26.2 Beta1 is the second pre-release since development of version 26.2 started at the beginning of June, 2025. Since the previous release, LibreOffice 26.2 Alpha1, 419 commits have been submitted to the code repository and 114 issues got fixed. Check the release notes to find the new features included in this version of LibreOffice.
LibreOffice 26.2 Beta1 can be downloaded for Linux, macOS and Windows, and it can be installed alongside the standard version.
In case you find any problem in this pre-release, please report it in Bugzilla ( You just need a legit email account in order to create a new account ).
For help, you can contact the QA Team directly in the QA IRC channel or via Matrix.
LibreOffice is a volunteer-driven community project, so please help us to test – we appreciate it!
Happy testing!!
…
As November started, we kicked off a new Month of LibreOffice campaign, celebrating community contributions all across the project. We do these every six months – so how many people got sticker packs this time? Check it out… 297 Excellent work! Hundreds of people, all across the globe, have helped
por Gustavo Pacheco El Festival Latinoamericano de Instalación de Software Libre (FLISoL) 2025 se llevó a cabo los días 25 y 26 de abril en Montevideo. El FLISoL es el evento descentralizado de Software Libre más importante de América Latina. Como miembro del Membership Committee de The Document Foundation, estuve
La Conferencia Global de LibreOffice 2026 se llevará a cabo en Pordenone, Italia, organizada por el PNlug (Grupo de Usuarios de Linux de Pordenone) y la Universidad de Pordenone, dentro del campus universitario. El evento comenzará el jueves 9 de septiembre y finalizará la mañana del sábado 11 de septiembre,
A modern C++ wrapper for the Firebird database API.Documentation | Repositoryfb-cpp provides a clean, modern C++ interface to the Firebird database engine. It wraps the Firebird C++ API with RAII principles, smart pointers, and modern C++ features.Features Modern C++: Uses C++20 features for type safety and performanceRAII: Automatic resource management with smart pointersType Safety:
LibreOffice Conference 2026 in Pordenone, Italy, and LibreOffice Conference 2027 in Gothenburg, Sweden LibreOffice Conference 2026 will be organised by PNlug (Pordenone Linux User Group) and the University of Pordenone in the city of Pordenone, on the university campus. The conference will begin on Thursday, 10 September and will end
After submitting a patch to LibreOffice Gerrit, one has to wait for the continuous integration (CI) to build and test the changed source code to make sure that the build is OK and the tests pass successfully. Here we discuss the situation when one or more CI builds fail, and how to handle that.
After you submit code to LibreOffice Gerrit, reviewers have to make sure that it builds, and the tests pass with the new source code. But, it is not possible for the reviewers to test the code on each and every platform that LibreOffice supports. Therefore, Jenkins CI does that job of building and testing LibreOffice on various platforms.
This can take a while, usually 1 hour or so, but sometimes can take longer than that. If everything is OK, then your submission will get Verified +1 .
Currently, these are the platforms used in CI:
gerrit_linux_gcc_releasegerrit_linux_clang_dbgutilgerrit_android_x86_64 and gerrit_android_armgerrit_windows_wslgerrit_macSome of the tests are more extensive, for example Linux / Clang also performs additional code quality checks with clang compiler plugins. Also, UITests are not run on each and every platform.
LibreOffice CI uses Jenkins
There can be multiple reasons for why a CI build fails, and give your submission Verified -1 . These are some of the reasons, and depending on the reason, solution can be different.
1. Your code’s syntax is wrong and compile fails
In this case, you should fix your code, and then submit a new patch set. You have to wait again for a new CI build.
2. The code’s syntax is OK, but it is not properly formatted
You should refer to the below TDF Wiki article and use clang-format tool to format your code properly.
3. Your code’s syntax is OK, but it logically not OK and fails some tests.
In this case, you should try fixing your code logic, and run the tests that fail and make sure they pass. After that, you may send a new patch set and wait for a new CI build.
4. Your code’s syntax and logic is OK, but some machine fails for other reasons like their disk being full or other software/hardware failures or hiccups
In this case, usually resuming the build can be a good option. You may ask on #libreoffice-dev or #tdf-infra IRC rooms for such a resume, or request access, if you submit many patches.
Resume build in LibreOffice CI
5. Your code’s syntax and logic is OK, but there are issues from other patches.
In this case, intervention from other LibreOffice developers is needed. Informing people on #libreoffice-dev can help, and then you have to re-base your submission in case new patches fix the build issue.
The best way to know the reason of the build failure is to look into …
| Imprint Privacy Policy | |
|
The Document Foundation is not responsible for the content on planet.documentfoundation.org. However - if you have any concerns about content please contact act Uwe Altmann for moderation. Copyright information: Unless otherwise specified in the author's blog, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the "Mozilla Public License v2.0". "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy. |
 |
| this site runs a modified version of planet.opensuse (https://github.com/openSUSE/planet.opensuse.org) © 2010 Pascal Bleser and the openSUSE Community. | |