Jump to: navigation, search


Revision as of 11:00, 11 February 2008 by Ruthdaly.ca.ibm.com (Talk | contribs)


Release Engineering and Build Wish List


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

Have a functional weekly build

  1. Done Process 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.
  2. Done Process change Developers must check in their code more frequently; i.e., at least weekly.




QA Team must be able to start testing before iteration end


COSMOS builds must be run on the eclipse server


  2. Done 216499 We need to document the build completely so that all committers know how to start a build manually.
  3. Done 216650 We need more disk quota.

COSMOS needs to be packaged according to adoption scenarios

    1. Need roles for the Data Collection component.
    2. Need roles for the Data Visualization component.
    3. 215357 215355 Resource Modeling bugzillas for refactoring
  3. 214774 209998 Fix other bugzillas for refactoring
  4. 218518 Involve the build team in helping with feature definition to enable an UpdateManager install.
  5. 216653 Create an update manager site for COSMOS

Generate reports and notifications of problems with the build

  1. 216591 Build "fire alarm" notification email
  2. 210263 Fix the copyright reporting tool
  3. 216630 Detect missing about.html and other files required by legal
  7. 216655 Generate Javadoc for milestone drivers
  9. 218050 Investigate running code coverage tool

We need agreement on the RE team's responsibilities

The COSMOS May 2007 F2F had the following discussion RE Responsibilities


COSMOS Release Engineering and Build

Bugs opened for the Build component

Build Packaging for COSMOS