Our community is preparing for the release of LibreOffice 6.0.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.
On December 22, 2017 we will have an international Bug Hunting Session (BHS), testing the RC1 version of LibreOffice 6.0.0. Please join us! :-)
When: December 22, 2017
Feel free to join us at any point during this Friday.
- Mentors will be most of the time available from 11:00 UTC to 15: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 RC release (LibreOffice 6.0.0 RC1) will be available until mid of January ;-)
How to Test it
1. Download LibreOffice 6.0 RC1.
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.
What to test
We aim to:
- Do as much testing on the 6.0.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!
macOS users: please check the dmg background and report any anomalies!
Windows users: please install LibreOffice without a pre-existing Universal C Runtime to verify that the fix for bug 108580 works.
There are always more ways to test: do your regular tasks, structured tests, or play with the new features..
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.0 features. Check, if there are meta bugs for the features to see what has already been reported.
- pick a component and check for bugs that were fixed in this release:
- <your refactoring here> ...
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 query, 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.
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!
If you have an idea for a test case, feel welcome to post this at our QA mailing list
Who's available to manage the connect via webchat channel? It would be great to have a couple of people providing coverage most of the day...
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!
- mkara: Mentoring.
|#||Participant's Name||Attending the Ankara Session?|
|1||Muhammet Kara (mkara): Mentoring||Yes|
|2||Gökhan Gurbetoğlu (ggurbet): Mentoring||Yes|
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 day :-)
- (your name here)
People working on this version
You can find the whole list of people working on this version here. Help us to test LibreOffice 6.0 RC1 and the next time the list will be updated you will appear on it ;-)