Jump to: navigation, search

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

(What we need)
Line 1: Line 1:
== What we need ==
+
== Release Engineering and Build Wish List ==
 +
=== What we need ===
 
<ol>
 
<ol>
 
<li>COSMOS needs to be packaged according to adoption scenarios:<br/>
 
<li>COSMOS needs to be packaged according to adoption scenarios:<br/>
Line 15: Line 16:
 
</ol>
 
</ol>
  
== What we have today ==
+
=== What we have today ===
 
[[COSMOS_RE_AND_BUILD|COSMOS Release Engineering and Build]]
 
[[COSMOS_RE_AND_BUILD|COSMOS Release Engineering and Build]]
  
== What will it take to get what we need ==
+
=== What will it take to get what we need ===
 
1. Before the build can act on this item, the following must happen:
 
1. Before the build can act on this item, the following must happen:
 
   1.1 Defining the use cases separated by roles (so that we know who needs what).  
 
   1.1 Defining the use cases separated by roles (so that we know who needs what).  

Revision as of 15:46, 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.1 Defining the use cases separated by roles (so that we know who needs what). 
      1.1.1 Need roles for the Data Collection component.
      1.1.2 Need roles for the Data Visualization component.
      1.1.3 Read first attempt to define these roles for the Resource Modeling component.
  1.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.2.1 Need to refactor the code for the Data Collection component as per its roles TBD above.
      1.2.2 Need to refactor the code for the Data Visualization component as per its roles TBD above.
      1.2.3 Resource Modeling bugzillas for refactoring:
            215357
            215355
      1.2.4 Fix other bugzillas for refactoring:
            214774
            209998

2. Fix existing bugzillas owned by the build team

            215273

3. Involve the build team in helping with feature definition to enable an UpdateManager install.