Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:v:version_control_system [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:v:version_control_system [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Version Control System ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Version Control System performs [[public: | ||
| + | |||
| + | The system records distinct Artifact revisions and preserves the relationships among them. | ||
| + | |||
| + | A Version Control System allows an authorized user or process to: | ||
| + | |||
| + | * Add an Artifact to Version Control | ||
| + | * Assign an identifiable revision | ||
| + | * Retrieve an identified revision | ||
| + | * Distinguish one revision from another | ||
| + | * Record a relationship between revisions | ||
| + | * Compare revisions | ||
| + | * Record changes to an Artifact | ||
| + | * Restore or reuse an identified revision | ||
| + | |||
| + | A Version Control System may manage: | ||
| + | |||
| + | * Source code | ||
| + | * Configuration files | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * Models | ||
| + | * Schemas | ||
| + | * Scripts | ||
| + | * Policy files | ||
| + | * Build specifications | ||
| + | * Documentation | ||
| + | |||
| + | A Version Control System differs from Version Control: | ||
| + | |||
| + | * [[public: | ||
| + | * A Version Control System is a system that performs that process | ||
| + | |||
| + | A Version Control System may include a repository, revision identification, | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //system that performs version control by recording identifiable revisions of artifacts and preserving the relationships among those revisions// | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Version Control System does not by itself establish that a revision is approved, released, deployed, authoritative, | ||
| + | |||
| + | A Version Control System may record information such as: | ||
| + | |||
| + | * Revision identifier | ||
| + | * Preceding revision | ||
| + | * Succeeding revision | ||
| + | * Change author | ||
| + | * Change timestamp | ||
| + | * Change description | ||
| + | * Repository location | ||
| + | |||
| + | The applicable requirements determine which information the system must preserve. | ||
| + | |||
| + | The term does not require a particular product, repository architecture, | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A Version Control System assigns an identifiable revision to an [[public: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||