Home » You searched for bug hunting session » Page 12

Search Results for: bug hunting session

LibreOffice monthly recap: April 2018

Lots of things are happening in the LibreOffice community – in development, documentation, design, QA, translations and much more. Here’s a summary of news and updates in April… LibreOffice 6.0.3 was released on April 3. It includes over 70 bug and regression fixes – see the release announcement for more details. From April 6 – 8, we had a LibreOffice community meeting and Hackfest in Hamburg. There were around 45 participants, who split into two groups. One group focused on a hackfest – a joint coding session. At the same time, a meeting of the German-speaking LibreOffice community took place. See here for the results of the hackfest, and what we discussed. We talked to Edmund Laugasson from the Estonian LibreOffice community about his efforts to promote free and open source software in his country. “ODF is quite widely used in Estonia – for instance, educational institutions usually have LibreOffice installed, along with some local authorities.” – Full interview here. Preparation began for the Month of LibreOffice, May 2018 – crediting contributions all across the project. If you’re a proud user of LibreOffice and would like to join our community, get involved! (We’ll even send you a cool sticker pack.)

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 Xisco Fauli… What has the QA community been working on in preparation for LibreOffice 6.0? During the development of LibreOffice 6.0, three Bug Hunting Sessions were held (6.0 Alpha1, 6.0 Beta1 and RC1), the last one just two weeks ago. There was also a parallel event organized by Muhammet Kara in Ankara, where volunteers gathered to test LibreOffice 6.0 RC1. Besides that, the QA team is constantly testing the latest daily builds, testing new features, and triaging the bugs reported on Bugzilla. What are your favourite new features in this release? That’s a difficult question, especially taking into account all the improvements done in this release to LibreOffice Android Viewer, to LibreOffice Online or the work done by the Google Summer of Code students among others. But if I had to choose one, I think I’d go for the characters dialog refactoring done by Akshay Deep and the UX (user

LibreOffice Conference 2017 in Rome – video wrap-up

This year’s LibreOffice Conference, held from 11 – 13 October, was a great success with over 200 attendees from around the world. Thanks to everyone who took part, and the hard-working organisers! Check out our short video wrap-up of the event: Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party. YouTube privacy policy If you accept this notice, your choice will be saved and the page will refresh. Accept YouTube Content With the conference finished, the community is now focused on LibreOffice 6.0, due for release in late January 2018. See the release notes for a list of new features and changes added so far, and join our upcoming Bug Hunting Sessions to help make it a really polished and robust release – stay tuned to this blog for details!

LibreOffice Community Weeks: Wrapping up

We’re already in to a new Month of LibreOffice, but in October we ran a series of Community Weeks, looking at what different teams in the LibreOffice project do, and how you can help them. So firstly, here’s a reminder of the articles, and then we’ll find out what effect they had… Documentation Meet the team Tools used, and how to get involved Development Our mentor for newcomers People, stats and tools Get involved Quality Assurance (QA) Meet the team Get involved Design Meet the team Recent changes, and communication Get involved   Feedback from the teams So what effect did the Community Weeks have on the projects? Here’s what each team had to say: Olivier Hallot (documentation): “The Community Weeks brought more people to the realm we are working in, and I had 3 new people showing up. One is a PhD professor from a university in India, who wrote a page on a set of Calc functions, and asked for more work. Another is a New Zealand national, involved in migrations and support, who is updating our books. I also got someone on IRC, but he did not came back. So overall, the week is positive, but we

Community Week: QA – get involved

Earlier this week we talked to LibreOffice’s quality assurance (QA) engineer, Xisco Fauli, about how the QA team works, what they’re involved with at the moment, and where they need help. Let’s now look at how regular LibreOffice users can get involved: even if you can only spare a little bit of time each week, you can really make a difference to strengthen and improve the software. LibreOffice’s QA team is comprised largely of volunteers. The team works through bug reports submitted by LibreOffice users, checking them for accuracy, reproducing them (where possible), and assigning them to the appropriate developers or projects. Reporting bugs Bugzilla is used for tracking bugs, and it’s a very versatile tool that may look a bit daunting initially. But once you’ve submitted a couple of bug reports it becomes easier to work with. To submit a bug report, you need to be logged in there – so click “New Account” at the top to set up an account. Now, let’s say you’ve found a bug in LibreOffice and want to report it. The process goes as follows: Click New at the top of Bugzilla, choose LibreOffice, and you’ll end up on this page Many bugs

Community Week: QA – meet the team

Having covered development and documentation, we’re now into our third LibreOffice Community Week: Quality Assurance (or just “QA” for short). QA is an essential element of the LibreOffice development process, and affects the suite in many ways. For the benefit of end users, QA helps to identify and fix bugs – whether they’re glitches in the behaviour of the office suite, or problems that arise when importing certain files, or just issues with the user interface. But QA is an integral part of new feature development as well. When a LibreOffice developer adds something new to the office suite, QA processes ensure that it doesn’t impact other features, and that the rest of the software continues to be stable and robust. LibreOffice has an active QA community that works on tracking, reproducing and fixing bugs, and The Document Foundation (the non-profit entity that backs LibreOffice development) recently hired a dedicated QA engineer, Xisco Fauli. We caught up with him to see how the QA process works and how newcomers can help out. What is your role in the QA team? My role is to act as a middle-man between the QA community and other teams, such as participating in the

Press Releases

Announcement of LibreOffice 25.8.4

Berlin, 18 December 2025 – LibreOffice 25.8.4, the fourth minor update to the free office suite developed by volunteers for…

Open Document Format

The Role of ODF in the Era of Digital Identity and Authentication

Digital identity has become an integral part of everyday life. We use it to access work tools and sign documents…