QA/BugHuntingSession/5.2.0RC1

Quick Start :
 * 1) Download: here! NOTE: Builds will be available at the time of the Bug Hunting Session
 * 2) Test what you want
 * 3) Find 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 5.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 translation for this version may not be over and is not yet integrated.

On June 24th we will have an international bug-hunting session, testing the RC1 of LibreOffice 5.2.0 Please join us! :-)

How to join

 * Get the latest version from the pre-releases server. NOTE: Builds will be available at the time of the Bug Hunting Session


 * Linux (32-bit):
 * DEB
 * RPM
 * Linux (64-bit):
 * DEB
 * RPM
 * Windows:
 * 32-bit
 * 64-bit
 * macOS:
 * 64-bit
 * Flatpak
 * flatpak

Note that it will *replace* your actual installation, this is a RC version that will install as a production version
 * Report bugs you find

When: June 24th
Feel free to join us at any point during these three days.


 * will be available from 07:00 UTC to 20:00 UTC on those dates.

If you can't join us during this session, you're always welcome to help us hunt for bugs on other days. The builds of this particular RC (LibreOffice 5.2.0. RC1) will be available until end of June ;-)

What to test
We aim at: There are always more ways to test: do your regular tasks, structured tests, or playing with the new features..
 * Doing as much testing on the 5.2.0 as possible
 * Triaging 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 5.2 features
 * pick a component and check for bugs that were fixed in this release: xx
 * Soon we will give some useful queries at this place, what will lead you to bugs that need some checking: xx
 * Things that underwent major refactorings between 5.1 -> 5.2:

Dedicated sessions
You want to participate for a short period of time or only on a dedicated module or only on a list of features, join us for this dedicated session that will happen between 15:00 and 17:00h UTC on Friday.

During the dedicated sessions, we will try to concentrate all our efforts together on one module, that will ease the reproduction, bring more fun to work together and at the end, we will have bugs confirmed or filled in a more complete manner.

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, which is 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:
 * Add it to BugZilla, or
 * Discuss it on QA/IRC
 * 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 at IRC and the mailing list to help with any question. Don't be shy, don't hesitate to ask!

More info on Moztrap, to work with our test cases, is here

If you have an idea for a test case, feel welcome to post this at our [mailto:libreoffice-qa@freedesktop.org QA mailing list]

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

Friday (24th)

 * sophi
 * (your name here)

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!

Friday (24th)

 * sophi: Mentoring.
 * (your name here): (what you want to test)

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 :-)

Badges

 * (your name here)