COSMOS RE AND BUILD WISH LIST
Release Engineering and Build Wish List
<mdw> Since we are opening up enhancement requests, we should tie these back to use cases per our development process. I think many of these, e.g. the download site, would support the idea of the CMDBf toolkit, as an example. </mdw>
What we need
- COSMOS needs have a continuous and well-defined build process -- Jimmy Mohsin
- Have a well-organized download page that is updated with a FUNCTIONAL build at least by the middle of each iteration (if not earlier).
- The download page must have a build that has ALL the components as soon as they become available. Even though this seems obvious, I state this explicitly since in the past, some components did not make it into the build even though they were available.
- The “new” build process will enable non-development teams, e.g. QA to pick-up a build DURING and (obviously) till the end of an iteration. This will enable the QA team NOT to have to wait till the end of an iteration for testing. E.g. QA could initiate the unit level testing BEFORE iteration end.
- With a continuous build process, we would be better positioned to address the iteration close build fire drills….
- COSMOS needs to be packaged according to adoption scenarios:
Read first thoughts on how to package COSMOS drivers
<mdw> This includes the creation of an update manager site for downloading the eclipse plug-ins that we provide. We would start with:
- SML Tooling
- WSDM Tooling
- Breaking API
- Legal issues:
- Missing copyrights
- Out-of-date copyrights
- Missing about.html files
- Dependencies not broken when new code added
What we have today
What will it take to get what we need
- Before the build can act on this item, the following must
- 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.