Difference between revisions of "COSMOS RE AND BUILD WISH LIST"
(→Release Engineering and Build Wish List)
(→What we need)
|Line 33:||Line 33:|
* SML Tooling
* SML Tooling
* WSDM Tooling
* WSDM Tooling
Revision as of 11:43, 23 January 2008
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 216211 -- 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). <mdw>I would advocate FUNCTIONAL build be available every week during an iteration. It should be considered a p1 on the project if we do not have this. I'd be willing to update the cosmos dev process as well.</mdw>
- 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
See also Build Packaging for COSMOS </mdw>
- Breaking API
- Legal issues:
- Missing copyrights
- Out-of-date copyrights
- Missing about.html files
<mdw> Like the BVT results, these should be made available via the web site as part of the daily builds. </mdw>
- Dependencies not broken when new code added
<mdw> Not sure where this fits, but we need to make sure we are running the build on the eclipse server and that we properly manage the space. A number of times we've received e-mails about exceeding our disk space quota. </mdw>
- Might be useful to have a list of bugs fixed in a particular driver? e.g. if a consumer wants to pick up a build, and they're waiting for a list of bugs to be fixed, this list would tell them what's done and they would be able to track what's outstanding.
- I've heard that the builds are not run on the eclipse server? That it's all set up and ready to go but not used yet? Would be nice to get that going.
- Generate reports during build to improve quality of code:
- CVS and bug activities
- API change reports
- Translation readiness
- Internal API usages
- Copyright problems in source code
- Plugin version number management reports
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.