Release Engineering and Build Wish List

<mdw>
Since we are opening up enhancement requests, we should tie these back to use cases per our development process. I think many of these, e.g. the download site, would support the idea of the CMDBf toolkit, as an example.
</mdw>

COSMOS needs to have a continuous and well-defined build process

Have a functional weekly build

Process change Developers must check the daily build to ensure that it is not broken.

Process change Developers must check in their code more frequently; i.e., at least weekly.

Process change Developers must use the build rather than relying on CVS alone. Developers must download the build regularly and check out only their plugins rather than relying on HEAD.

The download page must have a build that has ALL the components as soon as they become available.

This should be partly addressed by the actions for Have a functional weekly build. A developer will notice if their component is missing.

216169 Dependencies should be automatically be included in the build package

QA Team must be able to start testing before iteration end

Process change For example, if we decide that QA will always pick up a Friday build, then developers must check in their code by EOB Wed. Any problems with that build are fixed on Thursday and QA picks it up on Friday as scheduled.

COSMOS builds must be run on the eclipse server

This requirement is key to enable all committers to kick off a build.

206374 The infrastructure is set up; we can start running the builds on the eclipse server at any time. We should start this sooner rather than later. The earlier in a release we make build changes the more time that we have to react to the breakages that aren't expected but always occur.

216499 We need to document the build completely so that all committers know how to start a build manually.