Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "COSMOS RE AND BUILD WISH LIST"
m (→What will it take to get what we need) |
|||
Line 1: | Line 1: | ||
+ | <!-- breadcrumbs --> | ||
+ | [[COSMOS]] > [[COSMOS RE AND BUILD]] | ||
+ | |||
+ | <!-- CONTENT start --> | ||
== Release Engineering and Build Wish List == | == Release Engineering and Build Wish List == | ||
=== What we need === | === What we need === | ||
Line 68: | Line 72: | ||
enable an UpdateManager install.</li> | enable an UpdateManager install.</li> | ||
</ol> | </ol> | ||
+ | <!-- CONTENT end --> | ||
+ | |||
+ | <!-- Category --> | ||
+ | [[Category:Eclipse Technology Project]] [[Category:COSMOS]] |
Revision as of 17:12, 16 January 2008
Contents
Release Engineering and Build Wish List
What we need
- COSMOS needs to be packaged according to adoption scenarios:
Read first thoughts on how to package COSMOS drivers - 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
- 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
- Before the build can act on this item, the following must
happen:
- Defining the use cases separated by roles (so that we know
who needs what).
- Need roles for the Data Collection component.
- Need roles for the Data Visualization component.
- Read first attempt to define these roles for the Resource Modeling component.
- 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.
- Need to refactor the code for the Data Collection component as per its roles TBD above.
- Need to refactor the code for the Data Visualization component as per its roles TBD above.
- Resource Modeling bugzillas for refactoring:
- Fix other bugzillas for refactoring:
- Defining the use cases separated by roles (so that we know
who needs what).
- Fix existing bugzillas owned by the build team
- Involve the build team in helping with feature definition to enable an UpdateManager install.