Hey all,
Just had a nice talk with Sophi, here is the conversation summary:
QA People:
- Look forward to having more people on the list in 15/Apr IRC session.
Bug Triage:
- Looking for people as Focal Points for handling bugs written in non-English.
The role of focal points people is to help ping NL/l10n team asking
for a bug translation.
Before that, we could assign those bug to Sophi at the moment, we may
indicate these somewhere in wiki ;-)
Manual and Localization Testing:
- The most important thing is making Litmus running more reliably. We have a
willing to move most of the QA work to the system. It would be nice we all
follow the same process starting from 3.4 QA. Sophi will check the Litmus
deployment with Rimas.
- Sophi will contact with people to see if they are working on a general
process of testing. Yifan will scratch an outline if nobody is doing
it. Yifan is also interested in helping that done.
Automation Testing:
- We knew more people who is doing testtool automation work, we'll connect to
them.
- We need to figure out a way to put the testtool logs. Possibly include
this for Litmus management as well.
- Yifan can be one of the testool automation script maintainers:
http://wiki.documentfoundation.org/QA/QA_Team#QA_Team_volunteers_in_alphabetic_order
--
Yifan Jiang
Libreoffice
Contact: yifan - irc.freenode.net/libreoffice
=============================================
http://www.libreoffice.org/
http://www.documentfoundation.org/
Context
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.