QA/BugHuntingSession/5.3.0Beta2



Quick Start :
 * 1) Download: libreoffice-5-3 daily build ( Beta2 builds will be available during the time of the Bug Hunting Session )
 * 2) Test what you want
 * 3) Found a bug? Mention it on 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.3.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.

During December 9 and 10 we will have an international Bug Hunting Session (BHS), testing the version 5.3.0 of LibreOffice. Please join us! :-)

How to join
If beta2 is not yet available, please use the libreoffice-5-3 daily builds
 * Download LibreOffice 5.3.0 beta2 from here (Note that it will not replace your actual installation -- this is a development version that will not install as a production version.)


 * Test LibreOffice 5.3.0 beta2 in general or find more specific task here


 * Report bugs you find

When: December 9 and 10
Feel free to join us at any point during Friday and Saturday.


 * Mentors will be available from 08:00 UTC to 20:00 UTC on the 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 release (LibreOffice 5.3.0 beta2) will be available until week 51 ;-)

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 5.3.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!
 * Try to discover any problems with text rendering on macOS. The new font layout engine is enabled by default and has not been extensively tested on macOS. More on the layout change below.

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.3 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


 * Things that underwent major refactorings between 5.2 -> 5.3:
 * Text layout underwent a major refactoring to unify it accross platforms.
 * Watch for any text layout regressions from 5.2.
 * New features to test:
 * Layout with the same fonts should give the same result on all platforms.
 * Graphite fonts and vertical CJK text now work on macOS.
 * Default ligatures and kerning are enabled by default on Windows.
 * Verify if some bugs blocked by are now fixed.
 * For already reported problems regarding the new layout engine, see the meta bug dependency list.

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

Another session concerning a set of top 7 features to test will be organized between 17:00 and 19:00h UTC on Friday.
 * Writer Table Styles
 * Calc OpenXML Filter
 * SideBar
 * Area Fill Tab ( available in the Style, Paragraph, Area, Page, and Slide dialogs )
 * Firebird 3.0
 * GTK3 in general
 * Dark Themes in GTK+
 * Safe Mode ( Can be accessed via Help->Safe Mode; cmd line option --safe-mode, or the windows start menu entry "LibreOffice (Safe Mode)" )

During those dedicated sessions, we will try to concentrate all our efforts together. This will ease reproduction of bugs, make it 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 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
 * IRC
 * The 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 is available to manage the channel? It would be great to have a couple of people providing coverage most of the day...

Friday

 * sophi
 * buovjaga
 * (your name here)

Saturday

 * buovjaga
 * Xisco ( in the evening )
 * (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

 * sophi: Mentoring.
 * buovjaga: Mentoring
 * dennis: helping with q in irc
 * (your name here): (what you want to test)

Saturday

 * buovjaga: Mentoring
 * dennis: helping with q in irc
 * (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 :-)


 * (your name here)