Berlin, May 21, 2015 – The first LibreOffice 5.0 Bug Hunting Session
starts tomorrow at 08AM UTC, to catch bugs and regressions on the first
beta of the software, available from today from this link:
http://dev-builds.libreoffice.org/pre-releases/. The session will last
until May 24, 2015.
On those dates, mentors will be available from 08AM UTC to 10PM UTC to
help less experienced volunteers to triage bugs, on the QA IRC channel
and via email on the QA mailing list.
Those who cannot join during the bug hunting session are always welcome
to help chasing bugs and regressions when they have time. There will be
a second bug hunting session in June, to test LibreOffice 5.0 Release
Candidate 1.
More detailed information on the bug hunting session are available here:
https://wiki.documentfoundation.org/BugHunting_Session_5.0.0.0.
LibreOffice 5.0 will be released at the end of July 2015.
Link to blog post: http://wp.me/p1byPE-yl.
--
Italo Vignoli - email italo@documentfoundation.org
mobile +39.348.5653829 - jabber italo@libreoffice.org
hangout italo.vignoli@gmail.com - skype italovignoli
GPG Key ID - 0xAAB8D5C0
DB75 1534 3FD0 EA5F 56B5 FDA6 DE82 934C AAB8 D5C0
--
To unsubscribe e-mail to: announce+unsubscribe@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
List archive: http://listarchives.documentfoundation.org/www/announce/
Context
- [tdf-announce] First LibreOffice 5.0 Bug Hunting Session starts Tomorrow · Italo Vignoli
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.