Release contracts: Difference between revisions

From OLPC
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
 
Line 8: Line 8:
(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.)


[http://dev.laptop.org/report/18 Examples] are available.
[http://dev.laptop.org/report/18 Examples] are available. See our [[Trac conventions]] for help interpreting the display.

See our [http://dev.laptop.org/#Conventions Trac conventions] for help interpreting the display.

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