Hi Eike,
On 5 Jul 2007, at 15:59, 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?
Some form of extended tinderbox and buildbot setup, thus allowing the
install sets to be automatically produced when a CWS is set to "Ready
for QA". More resources will need to be put into this method for this
to work effectively.
We need at least one machine in each build configuration, on each of
the main platforms, compiling all the changes, and uploading the
install sets of the ready for QA CWSes.
I have personally found that running a bot on a production machine,
doesn't work too great, as you end up doing a change (such as
installing a new bit of software) and don't realise that it changes
the dependancies unexpectedly. It also means that when a clean
install of the OS is required to be able to get a clean environment
to get rid of any errors, you are less willing to go ahead and do it.
Shaun
[..]
___________________________________________________________
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]
