Our community is preparing for the release of LibreOffice 6.4.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 alpha version. So be careful with your data and don't test it with data you need for your daily work.
On October, 21, 2019 we will have an international Bug Hunting Session (BHS), testing the Alpha version of LibreOffice 6.4.0. Please join us! :-)
How to Test it
1. Download LibreOffice 6.4 Alpha.
NOTE: Links will be updated to point to the alpha 1 right before the bug hunting session.
- 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)
- Windows (64-bit)
- Mac OS X (64-bits)
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.
When: October 21, 2019
Feel free to join us at any point during this Monday.
- #Mentors 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 Alpha release (LibreOffice 6.4.0 Alpha) will be available until mid of May ;-)
What to test
We aim to:
- Do as much testing on the 6.4.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!
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.4 features
- pick a component and check for bugs that were fixed in this release:
- <your refactoring here> ...
Nothing planned yet
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 ticket system with a guided form to report bugs. If you are more confident with Bugzilla, you can report your bug using the [https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&bug_status=UNCONFIRMED 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!
Who's available to manage the #libreoffice-qa 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!
- xisco: Mentoring.
- buovjaga: Mentoring.
- Sophie. 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 day:-)
- (your name here)