Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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"
(→What will it take to get what we need) |
|||
| Line 20: | Line 20: | ||
=== What will it take to get what we need === | === What will it take to get what we need === | ||
| − | + | <ol> | |
| − | + | <li>Before the build can act on this item, the following must happen: | |
| − | + | <ol> | |
| − | + | <li>Defining the use cases separated by roles (so that we know who needs what). | |
| − | + | <ol> | |
| − | + | <li>Need roles for the Data Collection component.</li> | |
| − | + | <li>Need roles for the Data Visualization component.</li> | |
| − | + | <li>[[COSMOS_Use_Cases#SML_and_SML-IF_validation_support|Read first attempt to define these roles for the Resource Modeling component.]]</li> | |
| − | + | </ol> | |
| − | + | </li> | |
| − | + | <li>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. | |
| − | + | <ol> | |
| − | + | <li>Need to refactor the code for the Data Collection component as per its roles TBD above.</li> | |
| − | [http://bugs.eclipse.org/bugs/show_bug.cgi?id=209998 209998] | + | <li>Need to refactor the code for the Data Visualization component as per its roles TBD above.</li> |
| − | + | <li>Resource Modeling bugzillas for refactoring: | |
| − | + | <ul> | |
| − | + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=215357 215357]</li> | |
| − | + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=215355 215355]</li> | |
| + | </ul> | ||
| + | </li> | ||
| + | </ol> | ||
| + | </li> | ||
| + | <li>Fix other bugzillas for refactoring: | ||
| + | <ul> | ||
| + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=214774 214774]</li> | ||
| + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=209998 209998]</li> | ||
| + | </ul> | ||
| + | </li> | ||
| + | </li> | ||
| + | <li>Fix existing bugzillas owned by the build team | ||
| + | <ul> | ||
| + | <li>[http://bugs.eclipse.org/bugs/show_bug.cgi?id=215273 215273]</li> | ||
| + | </ul> | ||
| + | </li> | ||
| + | <li>Involve the build team in helping with feature definition to enable an UpdateManager install.</li> | ||
Revision as of 17:05, 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.
- 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.