Hi all,
After the few initial mails about this, and looking at 'the' agenda, I
propose the following:
Have either
a) a LibreOffice 4.0 Test Week from Monday 10 - Sunday 16th
or
b) a LibreOffice 4.0 Test marathon from Thursday 13 - Wednesday 19th
(A full week from 17-23 would be to close to Xmas, IMO).
With the promise that
- we mobilise as much people from our regular teams to show up for
support of new-bees;
- we of course provide comprehensive, clear info to get started;
- we focus both on random testing, scenario's and bug triage.
By spreading it over 7 days, it's easier for people to feel able to join :-)
Initial announcements would not be too hard. Could do that
Monday/Tuesday (evening).
Exchange among team members for availability can be done later this week.
Preparing info is rather easy...
Opinions?
Already promises maybe too :-)
Cheers,
Cor
Cor Nouws wrote (01-11-12 23:54)
Hi all,
Having some experience with this, I'm willing to try to help organising
something like a BHP again.
Starting from 'scratch' three goals come to my mind:
a - hunting bugs in 3.7
b - introducing people in submitting and triage of bugs
c - introducing people in (release) testing
wrt b and c: when we target for a BHP somewhere half December, would
that be fine for people working on the bug submission assistant and
Moztrap ?
Best,
Cor
--
- Cor
- http://nl.libreoffice.org
- www.librelex.org
Context
- 4.0 Test week/marathon Re: [...-qa] 3.7 bug hunt party ? · Cor Nouws
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.