Hi Jörn,
Jörg Jahnke schrieb:
I've not be active on this list yet, but rather (sparingly) on the
tools.dev or dev list, as I am normally more concerned with tooling
and release engineering issues. But the following is a proposal for a
change in the EIS (Environment Information System,
http://eis.services.openoffice.org/EIS2/servlet/GuestLogon) tool where
the intention is to get testers better involved in the process. So
I'll post it here instead of the tools.dev lists:
Thanks for bringing this to the list. This has been briefly discussed at
the conference and identified as one point of possible improofement.
Hope, we can go on with it.
....
The questions I have is:
- Would you use this feature and check the list of CWSs without QA
rep. and volunteer to do CWS testing?
I'm shure, people would do so (actually some members here are looking
for such a feature ore are even doing CWS tests)
- Is there a better way to solve the problem?
Well .. it's the first step to solve the problem. I'd like to put a
short draft of the process to the qa-project's website. I'd be happy if
someone could write a draft of the process. there should be also some
words about "what tests need to be done" and "how can I get the CWS for
testing".
- What about the last item above, am I right to say an email to the
CWS owner is the best way? Or would it be better to have the volunteer
automatically register as QA rep.?
Emails to the owner should be prefered. I think, there needs to be some
coordination between CWS owner and QA rep. If QA rep. just "pops up",
this could become difficult.
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
