Hi Martin,
Martin Hollmichel wrote:
Hi,
for a long time it has been already practice that not all child
workspaces had to be approved by a QA Team member but also by another
developer. The same applies for the involvement of the user experience
Team. Together with Lutz for the user experience team and Thorsten for
the QA team we review the existing Child Workspace policies on
http://tools.openoffice.org/dev_docs/child_workspace_policies.html.
With the help of Nikolai we are now able to provide a proposal for a
modified version of the child workspace policies on
http://wiki.services.openoffice.org/wiki/CWS_Policies
in the section 'Making the CWS "Ready for QA", "Approved by QA" and
"Nominated" for Integration', the role of the QA-representative is
defined wrong. Please refer included link
<http://wiki.services.openoffice.org/wiki/Approve_a_CWS>.
The QA-representative is not the to do the 'necessary tests', but the
person to coordinate the QA effort. This could even mean, that the QA
Rep. does no testing at all, when other tasks are on higher priority to
drive the process of CWS approval.
[...]
Best regards
Peter
--
Peter Junge
Program Manager and Senior Engineer Open Source Technology
北京红旗中文贰仟软件技术有限公司
Beijing Redflag Chinese 2000 Software Co., Ltd.
Building No.2, Block A, Huilongsen, 18 Xihuan South Street
Beijing Economic-Technological Development Area
Beijing, P.R.China
Tel：+86-10-51570010 ext.6212
http://www.ch2000.com.cn
http://www.ch2000.com.cn/english/index.htm
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
