Hi,
good work, but I miss the point where it is mentioned that there must be
a link to the installsets for the QA. This should not be a "nice to
have" but a "must", otherwise the QA representative has to ask the cws
owner for the installsets (with the delay which maybe occurs because of
different timezones etc.) or find someone who can build the installsets
locally.
Greetings, Oliver
Eike Rathke wrote:
Hi Martin,
On Wednesday, 2007-07-04 17:04:39 +0200, Martin Hollmichel wrote:
modified version of the child workspace policies on
http://wiki.services.openoffice.org/wiki/CWS_Policies
http://wiki.services.openoffice.org/wiki/CWS_Policies#Build_Configurations
| A CWS must be built on at least two platforms in the "product" version
| (Windows and one UNIX platform)
How will we ensure that non-Hamburg based CWSs can be built on these
platforms and install sets be made available?
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.
Nice work.
I suggest that we make this cws policies official on July 11th if there
are no objections until then.
+1 (given that the platform obstacle will be sorted out or handled relaxed)
I think some sections need to be checked against / merged with / link to
sections of http://wiki.services.openoffice.org/wiki/CWS which in some
aspects is more detailed, and in other aspects should be replaced with
the new policy.
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.
+1
Eike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
