public:99_annexes:annex-b-terms-and-definitions:v:version_control

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:v:version_control [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:v:version_control [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Version Control ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +Version Control manages changes to an [[public:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] by identifying distinguishable revisions and preserving the relationships among those revisions.
 +
 +Version Control allows an authorized user or process to:
 +
 +  * Identify a specific revision
 +  * Retrieve a specific revision
 +  * Distinguish one revision from another
 +  * Determine the relationship between successive revisions
 +  * Compare revisions
 +  * Associate a change with its recorded context
 +  * Restore or reuse an identified revision
 +
 +Version Control may apply to:
 +
 +  * Source code
 +  * Configuration files
 +  * [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configurations]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_blueprint|Infrastructure Blueprints]]
 +  * Models
 +  * Schemas
 +  * Scripts
 +  * Policy files
 +  * Build specifications
 +  * Documentation
 +
 +Version Control differs from a [[public:99_annexes:annex-b-terms-and-definitions:v:version_control_system|Version Control System]]:
 +
 +  * Version Control is the process used to manage revisions
 +  * A Version Control System is the system that performs Version Control
 +
 +Version Control also differs from approval, release management, deployment authorization, and records retention. Those activities may use revision information produced through Version Control but establish separate controls.
 +
 +===== Definition =====
 +
 +//process for identifying, recording, managing, and retrieving distinguishable revisions of an artifact and the relationships among those revisions//
 +
 +===== Source =====
 +
 +Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +===== Note =====
 +
 +Version Control does not by itself establish that a revision is approved, released, deployed, authoritative, or retained for a specified period.
 +
 +Version Control may preserve information such as:
 +
 +  * Revision identifier
 +  * Preceding revision
 +  * Change author
 +  * Change timestamp
 +  * Change description
 +  * Repository location
 +
 +The information preserved depends on the applicable Version Control process and [[public:99_annexes:annex-b-terms-and-definitions:v:version_control_system|Version Control System]].
 +
 +The term does not require a particular repository implementation, branching model, merge model, storage technology, or product.
 +
 +===== Example =====
 +
 +Version Control assigns an identifiable revision to an [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]], preserves its relationship to the preceding revision, and permits an authorized deployment workflow to retrieve the identified revision.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>