Release contracts: Difference between revisions
Jump to navigation
Jump to search
m (New page: A '''release contract''' is an agreement between the release team and one or more contributors to attempt to integrate some desirable change into a release build. Release contracts normal...) |
mNo edit summary |
||
| Line 3: | Line 3: | ||
Release contracts normally describe: |
Release contracts normally describe: |
||
* the required quality of an acceptable change, |
* the required quality of an acceptable change, |
||
* a test plan for judging the quality of a proposed change, |
* a test plan for judging the quality of a proposed change, and |
||
* who will execute the test plan |
* who will execute the test plan. |
||
* the consequences of breaking the "contract". |
|||
(Typically, violation of a release contract will result in deferral of the proposed change.) |
(Typically, violation of a release contract will result in deferral of the proposed change.) |
||
Revision as of 03:43, 14 June 2009
A release contract is an agreement between the release team and one or more contributors to attempt to integrate some desirable change into a release build.
Release contracts normally describe:
- the required quality of an acceptable change,
- a test plan for judging the quality of a proposed change, and
- who will execute the test plan.
(Typically, violation of a release contract will result in deferral of the proposed change.)
Examples are available.
See our Trac conventions for help interpreting the display.