version_control:introduction_to_version_control_systems
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
version_control:introduction_to_version_control_systems [2016/11/27 23:37] – mithat | version_control:introduction_to_version_control_systems [2019/02/21 18:48] – [Examples] mithat | ||
---|---|---|---|
Line 14: | Line 14: | ||
* [[https:// | * [[https:// | ||
* [[http:// | * [[http:// | ||
- | * [[http://www.nongnu.org/cvs/|CVS]]: A classic. Despised by many. | + | * [[http://subversion.apache.org/|SVN]]: "CVS done right," |
- | * [[http://subversion.apache.org/|SVN]]: "CVS done right." Once very popular. | + | * [[http://www.nongnu.org/cvs/|CVS]]: A classic and despised by many. |
===== Primary functions ===== | ===== Primary functions ===== | ||
* Create a **repository** to store all the source code for a project. | * Create a **repository** to store all the source code for a project. | ||
Line 57: | Line 56: | ||
* **revision**: | * **revision**: | ||
* When a meaningful change to the code of a project is completed, a **revision** incorporating that change is **committed** (placed) into the repository. | * When a meaningful change to the code of a project is completed, a **revision** incorporating that change is **committed** (placed) into the repository. | ||
- | * Also called **commits**, **snapshots**, and **changesets**. | + | * Also called |
* If needed, differences between the most recent state and older revisions can be determined. | * If needed, differences between the most recent state and older revisions can be determined. | ||
Line 79: | Line 78: | ||
===== Releases and versions ===== | ===== Releases and versions ===== | ||
- | * A revision that has has been published for general use is a **release** or a **version**. | + | * A **release** or a **version** |
- | * An arbitrary determination made by the developers, not necessarily a VCS concept. | + | * An arbitrary determination made by the developers, not necessarily a VCS concept. |
* Typically there are several revisions (commits) between releases/ | * Typically there are several revisions (commits) between releases/ | ||
Line 89: | Line 88: | ||
===== Semantic versioning ===== | ===== Semantic versioning ===== | ||
* [[http:// | * [[http:// | ||
- | * **{major}.{minor}.{path}** | + | * **{major}.{minor}.{patch}** |
- | * **major**: | + | * **major**: |
* **minor**: added functionality in a backwards-compatible manner. | * **minor**: added functionality in a backwards-compatible manner. | ||
* **patch**: backwards-compatible bug fixes. | * **patch**: backwards-compatible bug fixes. | ||
* Additional labels for pre-release and build metadata. | * Additional labels for pre-release and build metadata. | ||
- | * alpha release, beta release, release candidate. | + | * alpha, beta, release candidate. |
===== Microsoft version numbering ===== | ===== Microsoft version numbering ===== | ||
Line 111: | Line 110: | ||
===== Other versioning schemes ===== | ===== Other versioning schemes ===== | ||
- | * Some projects use date-based versioning, e.g.: '' | + | * Some projects use date-based versioning. |
+ | * '' | ||
+ | * '' | ||
* Whatever you do, be consistent and meaningful. | * Whatever you do, be consistent and meaningful. | ||
version_control/introduction_to_version_control_systems.txt · Last modified: 2019/02/21 18:52 by mithat