TDF Community Blog

LibreOffice proper

The year 2015 started off with LibreOffice 4.4.0 and 4.3.6 rc1 – only the first of a whopping 42 (of course!) tags that were created and for which a build was uploaded to our mirror network – and ends with the stable releases 4.4.7 and 5.0.4 and with the first RC for LibreOffice 5.1.0 (for those interested: that’s a total of 216GB for the binary builds).

This constant stream of builds allows our volunteer testers to always stay on top, not waste time with testing stuff only to find out a fix has already been checked in weeks ago.

But even the constant stream of full builds sometimes is not recent enough. Daily builds provided by various tinderboxes fill this gap. Not only do they constantly monitor the buildability of all current branches (and nag committers in case our continuous integration platform didn’t catch the problem before it ended up in the code), many also provide one installationset per day. That way users don’t have to fiddle with building LibreOffice themselves, but still can run the current code.

We also changed our release baseline:

• since LibreOffice 4.4 we require Mac OS X 10.8 or later and dropped the 32bit version

• since LibreOffice 5.0 we added 64bit builds for Windows (requiring Vista or later, 32bit build requires Windows XP SP3 or later)

• since LibreOffice 5.1 the new baseline for Linux is CentOS 6 (kernel 2.6.32 or later, glibc 2.12 or later)

Pootle

But the year was not only spent on LibreOffice alone. After having migrated bugzilla to our own infrastructure, it was time to tackle pootle. As mentioned in the last behind-the-scenes, we upgraded our version of pootle to run on TDF-hosted hardware and added master workflow. This allowed translators to start with their work for the 5.0 and subsequently 5.1 much earlier than with the old process (where translation could only begin after the branch was created).

Android

Good news everyone, there’s now a LibreOffice Viewer for Android! While still in its infancy, it is a first step to an editor application that you can use to give your documents the final touch when on the road.

If you own a smartwatch, then you also might be interested in the updated Impress Remote for Android, that now integrates with Android Wearable devices.

Hackfests

Continuing from last year, Hackfest-VMs were provided for the various gatherings that took place in 2015 and will be provided to those happening in 2016. Participants don’t have to roll thumbs waiting until the build is finished on their personal machines, but can instead start digging into the code on a fast virtual machine, and also do some bibisecting to warm up/find an easy entry point.

tl;dr

• nearly one LibreOffice build per week on top of that daily builds from tinderboxes

• Impress Remote for Android got support for Wearables

• LibreOffice Viewer for Android with basic editing capabilities

• Bugzilla was migrated to TDF-Infrastructure

• Pootle server was upgraded and moved to TDF-Infrastructure, with translators now being able to work on master branch

LibreOffice QA has been busy during the last few months!

We had our first BugHunting Session for the upcoming LibreOffice 5.1 release over the Halloween weekend at the end of October. Testing our alpha1 builds, members of the QA Team helped to lead users, developers, and other community members in identifying and documenting problems in our very first binaries available for this release series. Having support from members of QA, L10n, Developers, members of the Design community, and regular LibreOffice users was a great sign for continued cross-team participation. We’re looking forward to seeing a similar mix of contributors during our next BugHunting Session coming up this weekend.

We identified 104 bugs during the Halloween BugHunting session, primarily from initial testing with the alpha1. Of the 74 of bugs remaining open, 80% have been triaged to previous versions, leaving only 15 bugs tied to LibreOffice 5.1. Looking at all 5.1 versions, there are only 212 open bugs pegged to this release series, with only 44 open bugs pegged against 5.1 alpha1.

We’ve been busy with regression-hunting, performing over 550 bibisects this year, and over 200 since June. With one of our chief regression hunters and bibisect sorcerer Matthew Francis taking a well-earned respite from the cauldron of crafting new bibisect repositories and hacking on Python internals, we’re actively recruiting new QA members to help perform these binary searches on all platforms.

In fact, with so many of our developers (and other community members) using Free Software operating systems on their workstations, there’s always a need for contributors who are running MS-Windows or OS X to help us track down OS-specific bugs. This includes not only performing bibisects, but also debugging and getting a backtrace for a crashing bug.

Keeping our UNCONFIRMED bug count steady has been challenging. Currently hovering in the mid-500s, other important QA tasks and processes have commanded our time, and we could benefit from several more QA Team members to help shoulder the daily influx of new, untriaged bug reports. With the focus of our regular BugHunting Sessions on finding and identifying new issues in our upcoming builds, we may find it useful to host similar events that focus wholly on triage and “gardening” of the mass of existing reports in Bugzilla. Maybe we could have something like “Clean Sweep Mondays,” where we tackle the existing clutter for a set period of time, and post some quick stats such as total drop in UNCONFIRMED, # of NEEDINFO cleaned up, etc.

Work continues on our comprehensive Media Support wiki pages, a collection of tests designed to directly verify the level of support for various image, audio, video, (and other) file formats across all of our platforms. Keeping these pages up to date ensures that they continue to be a resource for QA bug triaging as well as for our volunteers helping to answer questions on the Ask LibreOffice site. Lead by QA Team member raal, we now have initial image test results for Android, and are interested in talking with developers who’d like to expand the Android Viewer’s capabilities in this area, as well as testers who would like to expand our battery of test results for the Android OS.

This weekend (Fri, Sat, Sun), we’re holding our BugHunting Session for the 5.1 Beta1 build. For those of you who are interested in kicking the tires and working with a still-rough-around-the-edges piece of software, your help is greatly appreciated. With a large package such as LibreOffice, it’s invaluable to have the technical members of our userbase exercise some of the more esoteric features of LibreOffice, and identify any minor regressions or usability concerns early-on in the release process.

The QA Team looks forward to seeing you in IRC anytime, or stopping by one of our weekly Wednesday meetings. We’re always happy to answer your questions about bug reports, bibisecting, etc., and to helping new contributors get started with the LibreOffice community!

LibOCon in Aarhus, Denmark, has been a really nice meeting especially for the L10n/NLP communities with a large workshop on the day before the opening of the conference. Even the whole afternoon was too short to discuss all the topics we had on the agenda. Around 40 persons from all over the world were attending the meeting. We have shared experiences and feedback, Christian has explained the new workflow with master and how branching is managed, and discussed some Pootle enhancements as well as other enhancements on coordination.

At the end of the meeting we discussed a specific issue with accelerators that are broken in some languages and specifically in languages using complex script layouts. This has led Niklas Johansson to develop a tool that detects duplicate use of accelerator keys in menus. This tool is of great help for all of us, translators, but also for our users and even more when accessibility matters. Thanks so much Niklas for this!

If you missed the conference, you’ll find all the videos of the talks on the TDF channel [1], there has been a whole track about localization, migrations and marketing. Italo has also organized marketing workshops dedicated to NLPs.

As a direct consequence of this meeting, we have opened a NLP channel on IRC, still too quiet in my opinion, don’t hesitate to join us and say hello! on Freenode #libreoffice-NLP, we will be happy to meet you there.

This meeting has also encouraged the Native Language projects to give more feedback on what they are doing locally, so far we have news about events in Korea, Turkey, Albania, India, Singapour, Sri Lanka… ans still feedback from the very active communities in Japan and in Italy where a first hackfest has been organized.

In more details, the Turkish community has participated to the DevFest in Istambul, giving an introduction on LibreOffice developments. I’d like to highlight the work done by Kader Tarlan who has written almost 50 new tests for MozTrap, and is currently working on porting java tests to python, a big big thank you to her!

The L10n community has extended its translations to some part of the tools we are using and has provided translations for Redmine and Ask in a very timely manner. I’m very happy to see the reactivity of our project especially during the translation sprint of the next version, namely the LibreOffice 5.1 release. This release has had a lot of changes in its off line help, it’s a very good thing (thanks a lot to Lera Goncharuk and Olivier Hallot!) but that means also a bunch of work for the localizers. Chandrakant Dhutadmal, representing the Centre for Development of Advanced Computing, has took the lead on several Indian languages in Pootle and will try to revive their localization, that’s a really nice initiative, thanks also to him.

I wish to all a happy holiday period and see you next year!

[1] https://www.youtube.com/channel/UCQAClQkZEm2rkWvU5bvCAXQ