[stp-dev] Requirements for the build.

["Oisin Hurley" <oisin.hurley@xxxxxxxxx>]

I'd like to open up some discussion on the way we build things right
now and ask for opinions, advice, and eventually, help.

Our build will be changing to accomodate the various SVN changes
and now is the team to think about greater change and flexibility.

The question is, what do you want from it?  Cruisecontrol,
hudson build-on-change is very useful, as is a regular full build
and test schedule. Documentation is a must, as is the capability
for developers to build from the command line locally on their
own machine. An automatically generated home page is the
norm for other projects too, so something like that is necessary.

What else? For example, right now the build is just one big blob,
wherein everything gets constructed. I'd suggest that build-per-
component and build-per-project seems to be a better idea. A
full roll-up build can be useful, but follows a different schedule,
i.e. it will consume from the individual builds.

Also, there's platforms - 3.3.2 anyone? Certainly 3.5, that's
mandatory, but maybe people want 3.4.x stream builds too?|

For EID, I would like to have regular 3.4.x, 3.5.x stream builds,
with test and coverage reports, and be able to build on my
local machine, outside of the UI. Consumption then by update
site is good. I'd like a separate download page for EID, linked
from a top level STP page, kind of like the way Modeling does
theirs. Also, a list of the dependencies would be very useful.

Comments?  Can we create a plan?

 --oh