QA/BugHuntingSession/6.2.0Beta



Quick Start :
 * 1) Download: here!
 * 2) Test what you want
 * 3) Found a bug? Mention it on QA/IRC or file a bug!

It's as simple as that -- your help is greatly appreciated!

Intro
Our community is preparing for the release of LibreOffice 6.2.0. We've added many new features and fixed loads of bugs (see below...), and we want to make sure that the new version is well-tested. You can help to make this release a great one!


 * Be aware however that the translations for this version are still being done and are not yet integrated.
 * Be aware however that it is an Beta version. So be careful with your data and don't test it with data you need for your daily work.

On November 19, 2018 we will have an international Bug Hunting Session (BHS), testing the Beta version of LibreOffice 6.2.0. Please join us! :-)

How to Test it
1. Download LibreOffice 6.2 Beta


 * Linux (32-bit):
 * Main .DEB Package - Other .DEB Packages (langpack, helppack)
 * Main .RPM Package - Other .RPM Packages (langpack, helppack)
 * Linux (64-bit):
 * Main .DEB Package - Other .DEB Packages (langpack, helppack)
 * Main .RPM Package - Other .RPM Packages (langpack, helppack)
 * Appimages with and without help
 * Windows (32-bit):
 * Main .MSI Package - Other .MSI Packages (langpack, helppack)
 * Windows (64-bit):
 * Main .MSI Package - Other .MSI Packages (langpack, helppack)
 * Mac OS X (64-bits):
 * Main .DMG Package - Other .DMG Packages (langpack, helppack)

2. Install it. (Note that it will not replace your actual installation -- this is a development version that will not install as a production version.)

3. Test it.

4. Report bugs you find. (For help, join in IRC

When: November 19, 2018
Feel free to join us at any point during this Monday.


 * will be available from 07:00 UTC to 19:00 UTC on that date.

If you cannot join us during this session, you are always welcome to help us hunt for bugs on other days. The builds of this particular Beta release (LibreOffice 6.2.0 Beta) will be available until mid of December, 2018 ;-)

What to test
We aim to: There are always more ways to test: do your regular tasks, structured tests, or play with the new features..
 * Do as much testing on the 6.2.0 as possible
 * Triage all already-filed issues for this version, so that it's as clear as possible for the developers to step in!

Choose what suits best for you :-) All testing is great and important, and the more we are, the more chance we have to hunt a bug!

So take one of those:
 * Your own favourite features
 * Look at the new 6.2 features
 * pick a component and check for bugs that were fixed in this release:
 * Base
 * BASIC
 * Calc
 * Chart
 * Draw
 * Printing and PDF Export
 * UI
 * Writer



Dedicated sessions
You want to participate for a short period of time or only on a dedicated module, join us for any of the three dedicated sessions that will happen between 11:00 and 13:00h UTC and 13:00 and 15:00h UTC and 15:00 and 17:00h UTC on Monday.

During these dedicated sessions, we will focus again on the new KDE5 Integration and the tabbed notebookbar and Base Firebird support.

KDE5
Between 11:00 and 13:00h UTC.

Before you report a new bug, make sure it hasn't been reported yet. The easiest way is to check in it's not in listed in the KDE metabug

This is the list of bugs already fixed in this release.

Firebird DB / Access2Base
Between 13:00 and 15:00h UTC.

Firebird RDBMS support in Base becomes non experimental in this release. Access2Base bundled library adds full support for Firebird 3.0.

Before you report a new bug, make sure it hasn't been reported yet. The easiest way is to check in it's not in listed in the

Firebird Support metabug

Firebird Migration Assistant metabug

Tabbed Notebookbar
Between 15:00 and 17:00h UTC.

The tabbed notebookbar became non experimental in this commit.

Before you report a new bug, make sure it hasn't been reported yet. The easiest way is to check in it's not in listed in the KDE metabug

Found a bug?
At first, make sure it isn't already reported by searching in our bug database. If it isn't reported yet, you can add it to our bug database using our [https://bugs.documentfoundation.org/enter_bug.cgi?format=guided&product=LibreOffice ticket system with a guided form to report bugs. If you are more confident with Bugzilla, you can report your bug using the Bugzilla interface. When you want to discuss first, use chat or mail, fast and direct.

So:
 * Report it to BugZilla
 * Discuss it on
 * Via the QA/Mailing List

If there is a bug that you want to pin point as clear as possible, then bibisect (explained by Bjoern Michaelsen) will be a great tool for you (for advanced testers)!

Get a little support
Other users and testers are on IRC and the mailing list to help with any question. Don't be shy, don't hesitate to ask!

Mentors
Who's available to manage the channel? It would be great to have a couple of people providing coverage most of the day...

Monday

 * Xisco
 * buovjaga
 * Bearon
 * Sophie
 * mkara
 * ggurbet

Participants
Joining us for Bug Hunting Fun?

It'd be very helpful for us if you could register for the TDF Wiki and add your name or IRC nick below. This helps us keep track of participation in the event, and gives us stats to help us plan our next Bug Hunting event!

Monday

 * xisco: Mentoring.
 * buovjaga: Mentoring.
 * Sophie. Mentoring.
 * mkara. Mentoring.
 * ggurbet. Mentoring.
 * djredaux. (Mentoring - Dedicated Base Session)
 * deneb_Beta: Mentoring.

I don't want to commit to a particular day!
For those of you who like to keep things loose and fluid, please add your name (and/or IRC nick) below. We're looking forward to seeing you in #libreoffice-qa at some point during the weekend :-)


 * (your name here)

Banners