<li><b>Process change</b> Developers must check the daily build to ensure that it is not broken.</li>

+

<li><b><font color="green" size="+1">Done</font></b> <b>Process change</b> Until the "fire alarm" email is automated, the build team will manually email cosmos-dev@eclipse.org to notify developers when there is a compile error. Upon seeing a build break email, developers must check the build reports to fix the problem. The Build Reports, which are listed in a link next to the driver link on the download page, provide more details.</li>

−

<li><b>Process change</b> Developers must check in their code more frequently; i.e., at least weekly.</li>

<li><b>Process change</b> 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.</li>

+

<li><b><font color="green" size="+1">Done</font></b> <b>Process change</b> 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.</li>

<li>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=215135 215135] Establish a process for running JUnits against a COSMOS build</li>

<li>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=215135 215135] Establish a process for running JUnits against a COSMOS build</li>

</ol>

</ol>

+

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

== 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 <i>Have a functional weekly build</i>. A developer will notice if their component is missing.

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

Line 33:

Line 34:

<ol>

<ol>

<li>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=206374 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.</li>

<li>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=206374 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.</li>

−

<li>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=216499 216499] We need to document the build completely so that all committers know how to start a build manually.</li>

+

<li><b><font color="green" size="+1">Done</font></b> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=216499 216499] We need to document the build completely so that all committers know how to start a build manually.</li>

<li>Involve the build team in helping with feature definition to enable an UpdateManager install.</li>

+

<li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=215610 215610] Involve the build team in helping with feature definition to enable an UpdateManager install and create an update manager site for COSMOS</li>

−

<li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=216653 216653] Create an update manager site for COSMOS</li>

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

DoneProcess change Until the "fire alarm" email is automated, the build team will manually email cosmos-dev@eclipse.org to notify developers when there is a compile error. Upon seeing a build break email, developers must check the build reports to fix the problem. The Build Reports, which are listed in a link next to the driver link on the download page, provide more details.

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

DoneProcess 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

DoneProcess change We need to have a weekly integration build. Build schedule

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.

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