drummyfish/less_retarded_wiki
5
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update

Browse source
This commit is contained in:
Miloslav Ciz 2025-07-21 04:11:02 +02:00
parent 895f96a007
commit 531fb64cc1
34 changed files with 2009 additions and 1971 deletions
Download patch file Download diff file Expand all files Collapse all files

8
version_numbering.md
View file

@ -1,14 +1,10 @@
# Version Numbering
Version numbering is a [system](system.md) of assigning [numbers](number.md) (or even general text [strings](string.md)) to different versions of computer programs or similar [projects](project.md). The basic purpose of this is to distinguish different versions from each other while also knowing which one is newer (more "[up to date](update_culture.md)"), however version identifiers often go further and provide more [information](information.md) such as the exact release date, whether the version is [stable](stability.md) or testing, with which other versions it is [compatible](compatibility.md) and so on.
TODO
Version numbering is a [system](system.md) of assigning [numbers](number.md) (or even general text [strings](string.md)) to different versions of computer programs or similar [projects](project.md). The basic purpose of this is to distinguish different versions from each, mark them for easy identification and potentially enable actions such as comparing which version is newer (more "[up to date](update_culture.md)"), which ones are stable or [compatible](compatibility.md) with each other and so on.
## Traditional Version Numbering
Possibly the most widely used system is that which marks versions as *major.minor*, where *major* is a number specifying very BIG changes, and *minor* is a number marking smaller ones. It's not uncommon to see three numbers: *major.minor.patch*, where *patch* signifies yet smaller changes such as hotfixes of bugs. The versions *0.x* usually stand for unfinished, alpha/beta releases, whereas *1.0* signifies the first "completed" release that has met all the initial goals. *2.0* may stand for a complete reimplementation etc.
TODO
Possibly the most widespread system is that which marks versions as *major.minor*, where *major* is a number indicating BIG changes and *minor* marking smaller ones. It's not uncommon to see this extended to a triple of form *major.minor.patch*, where *patch* signifies yet smaller changes such as hotfixes of bugs. The versions *0.x* usually stand for unfinished, alpha/beta releases, whereas *1.0* signifies the first "completed" release that has met all the initial goals. *2.0* may stand for a complete reimplementation or rework etc. [Hashes](hash.md) may be used in version numbers as well. Text strings are sometimes seen too, for example "RC" may stand for "release candidate".
## LRS Version Numbering Systems