minetest
/
minetest
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

README.md: Improve version scheme text (#7465)

master
Paramat 2018-06-20 13:11:13 +01:00 committed by GitHub
parent 2e95ebd181
commit 525fa9145e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@ -70,7 +70,6 @@ Some can be changes in the key config dialog in the settings tab.
Paths
-----
Locations:
* bin - Compiled binaries
@ -110,7 +109,6 @@ Command-line options:
Compiling
---------
### Compiling on GNU/Linux
#### Dependencies
@ -430,12 +428,15 @@ This is how we build Windows releases.
Version scheme
--------------
We use major.minor.patch since 5.0.0-dev. Prior to that we used 0.major.minor.
Minetest partially follows semver (major.minor.patch).
- Major is incremented when the release contains breaking changes, all other
numbers are set to 0.
- Minor is incremented when the release contains new non-breaking features,
patch is set to 0.
- Patch is incremented when the release only contains bugfixes and very
minor/trivial features considered necessary.
Since 5.0.0-dev and 0.4.17-dev, the dev notation refers to the next release,
ie: 5.0.0-dev is the development version leading to 5.0.0.
Prior to that, we used oldversion-dev.
Semver was adopted after 0.4.X series. Before that we used 0.major.minor scheme.
ie: 5.0.0-dev is the development version leading to 5.0.0.
Prior to that we used previous_version-dev.