Show pageOld revisionsBacklinksAdd to bookExport to PDFODT exportBack to top This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. ====== Revision ====== [[dido:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]] ===== Discussion ===== A Revision is an identifiable state of an [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] that results from one or more changes. A Revision allows an actor or process to distinguish a particular Artifact state from earlier or later states of the same Artifact. A Revision may apply to: * Source code * Documentation * Models * Schemas * Policies * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configurations]] * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_blueprint|Infrastructure Blueprints]] * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]] * Build specifications * Deployment specifications A Revision may include or reference: * A revision identifier * The Artifact content associated with the Revision * The preceding Revision * The change author * The change timestamp * A description of the change * The applicable approval or release state The applicable requirements determine which information must accompany a Revision. A Revision differs from a version: * A Revision identifies a distinguishable Artifact state produced through change * A version may identify a Revision selected, labeled, packaged, or released for a defined purpose A project may use the terms interchangeably when its governing conventions explicitly define them that way. ===== Definition ===== //identifiable state of an artifact resulting from one or more changes// ===== Source ===== Dido Solutions, Inc. and Jackrabbit Consulting, Inc. ===== Note ===== Creation of a Revision does not by itself establish that the Revision is: * Approved * Released * Deployed * Authoritative * Compliant * Suitable for a specified purpose Separate requirements or governance decisions establish those characteristics. A [[dido:99_annexes:annex-b-terms-and-definitions:v:version_control_system|Version Control System]] may assign and manage Revision identifiers. ===== Example ===== A change to an Infrastructure Configuration produces a new Revision with an identifier that distinguishes the changed configuration from its preceding state. ---- <WRAP centeralign> © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. </WRAP> dido/99_annexes/annex-b-terms-and-definitions/r/revision.txt Last modified: 2026/07/16 11:58by nick_dido