Skip to main content
Jump to: navigation, search

Difference between revisions of "COSMOS RE AND BUILD WISH LIST"

m (What will it take to get what we need)
Line 47: Line 47:
<li>Resource Modeling bugzillas for refactoring:
<li>Resource Modeling bugzillas for refactoring:
<li>[ 215357]</li>
<li>[ 215355]</li>

Revision as of 17:15, 16 January 2008


Release Engineering and Build Wish List

What we need

  1. COSMOS needs to be packaged according to adoption scenarios:
    Read first thoughts on how to package COSMOS drivers
  2. The build needs to detect stop-ship problems and send out notifications:
    • Breaking API
    • Legal issues:
      • Missing copyrights
      • Out-of-date copyrights
      • Missing about.html files
    • Dependencies not broken when new code added
  3. Build Verification Test (BVT) run and results posted for everyone to see

What we have today

COSMOS Release Engineering and Build

What will it take to get what we need

  1. Before the build can act on this item, the following must happen:
    1. Defining the use cases separated by roles (so that we know who needs what).
      1. Need roles for the Data Collection component.
      2. Need roles for the Data Visualization component.
      3. Read first attempt to define these roles for the Resource Modeling component.
    2. The code must be refactored so that the build can package the code the way that we think that a consumer intends to use it.
      1. Need to refactor the code for the Data Collection component as per its roles TBD above.
      2. Need to refactor the code for the Data Visualization component as per its roles TBD above.
      3. Resource Modeling bugzillas for refactoring:
    3. Fix other bugzillas for refactoring:
  2. Fix existing bugzillas owned by the build team
  3. Involve the build team in helping with feature definition to enable an UpdateManager install.

Back to the top