TDF LibreOffice Document Liberation Project Community Blogs Weblate Nextcloud Redmine Ask LibreOffice Donate
|The LibreOffice community is preparing the release of 3.6.0. There is a load of good new stuff prepared (more below...) and we want to make sure that it is well tested. You can now help to make version 3.6.0 a great one! At July 6 and 7 we have an international bug-hunting session with the third beta for LibreOffice 3.6.0. Join :-)|
How to join
- Get the latest version (LibreOffice 3.6.0 Beta)
- Report bugs you find
When: July 6 and 7
Any time you want ... however:
- Mentors are supposed to be available from 08:00 UTC to 22:00 UTC on both dates.
When you are not able to join this session, you're of course always welcome to hunt bugs at other dates/times ;-)
What to test
We aim at
- doing as much testing on the 3.6.0 as possible
- triaging all already filed issues, 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 playing with the new features..
Choose what suits best for you :-) All testing is great and important!
So take one of those:
- your own favorite features
- look at the new 3.6 features
- pick up a test case from the standard regression test
- Soon we will give some useful queries at this place, what will lead you to bugs that need some checking:
Find a bug?
When you are really sure: add it to our bug database. When you want to discuss it, use chat or mail, fast and direct.
- Add it to BugZilla , or
- discuss it on irc
- new with IRC chat? read this for help, and see Wikipedia. We are on the Freenode #libreoffice channel. Click on the #libreoffice IRC channel or irc://chat.freenode.net/libreoffice
- via 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!
Get a little support
Other users, testers, are at irc and the mail list to help with any question.
More info on Litmus, to work with our test cases, is here
If you have an idea for a test case, feel welcome to post this at our QA mailing list