I think a Build need not be an executable or even an operational integration, e.g. Builds that are libraries or partial integrations. Also, there will be multiple builds but 1 release per iteration.
How about: "A build is an aggregation of related compiled code segments that can be managed as a unit"? "A release is an executable aggregation of related compiled code segments and corresponding supporting documentation that can be published as a unit." Releases could be further classified as internal, external, iteration, and project end. I have also seen releases that were external at iteration milestones, esp in product development. -------------------------- Sent from my BlackBerry Wireless Handheld -----Original Message----- From: [EMAIL PROTECTED] To: [email protected] Sent: Thu Sep 07 16:16:17 2006 Subject: [epf-dev] term definition Hi, while preparing some PM content for burndown and phases, I needed to decide on two terms. Here are my suggestions. "Build" (commonly an iternal executable after each iteration, occassional external for verification purposes) "Release" (term for external release when the project transitions out... could be pre, beta or production release) I suggest removing the term "release" in OpenUP after each iteration and replace it with "build". Thoughts? Agreement? Joe Confidentiality Statement: This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by return email. _______________________________________________ epf-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/epf-dev
