Revision as of 16:37, 17 January 2008

Contents

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

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….

<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>