Hi,
I have a few questions/clarifications that might be needed for the
page, some of these points that I raise are for newbies who may be
directed to the page:
The Team: How to group people
* Can you please expand on the "four eyes principle", is it simply
that at least 4 different people should take a look at changes.
Build Configurations
* What is the difference between "product" and "non-product" builds?
Please include a link to an explanation on the difference.
Synchronization with Master Workspace
* There is no link to instructions of how to do a resync, only
information on how to access EIS.
Making the CWS "Ready for QA", "Approved by QA" and "Nominated" for
Integration
* It is not clear enough that "Approved by QA" == "Nominated".
Making the CWS "Ready for QA"
* The smoke test doesn't work on the Mac, and there are issues
running it on other platforms sometimes. What does the smoke test
actually do?
* Can there be more information on Changes-Mails? Maybe just a like
to some other documentation.
Setting a CWS to "Approved by QA"
* I've changed the links to wiki style links, so that the document
looks better.
Integration
* I don't understand the bit after the and in "If this is not
resolvable, the CWS is rejected and the MWS returns to the last
milestone before."
Integrated CWS
* The code changes are also stored in CVS too.
Appendix:
* What is a "master child workspace"? Shouldn't that be a "master
workspace"?
Shaun
On 4 Jul 2007, at 16:04, 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
The main difference compared with the old policies are
* How to group task goes now much more in detail to make more clear
in which cases what people are needed to review the work on a child
workspace.
* added more links to documentation on "how to approve a CWS"
* removed superfluous wording and sentences.
I suggest that we make this cws policies official on July 11th if
there are no objections until then.
If these changes get accepted I propose to exchange the "Level of
impact" in the EIS application accordingly to the new
categorization of cws in the policies.
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
___________________________________________________________
All New Yahoo! Mail Tired of [EMAIL PROTECTED]@! come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]