summaryrefslogtreecommitdiff
path: root/doc/versioning.md
diff options
context:
space:
mode:
authorRiku Isokoski <riksu9000@gmail.com>2021-11-08 17:38:21 +0200
committerJF <JF002@users.noreply.github.com>2021-11-28 13:42:37 +0100
commit5eaae4175c19f0e2752d3e27372f5aa578dec980 (patch)
tree03d5f1cc5d77ca3dec74a075c57ff4dcaa727ccd /doc/versioning.md
parente53f1bfd668a5c130352616aceb6c660821dc14c (diff)
Fix versioning
Diffstat (limited to 'doc/versioning.md')
-rw-r--r--doc/versioning.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/versioning.md b/doc/versioning.md
index 48e05043..8b87d473 100644
--- a/doc/versioning.md
+++ b/doc/versioning.md
@@ -1,6 +1,6 @@
# Versioning
-The versioning of this project is based on [Semantic versionning](https://semver.org/) :
+The versioning of this project is based on [Semantic versioning](https://semver.org/):
- The **patch** is incremented when we fix a bug on a **released** version (most of the time using a **hotfix** branch).
- The **minor** is incremented when we release a new version with new features. It corresponds to a merge of **develop** into **master**.
- - The **major** should be incremented when a breaking change is made to the application. We still have to define what is a breaking change in the context of this project. For now, I suggest that it stays **0** until we have a fully functioning firmware suited for the final user. \ No newline at end of file
+ - The **major** should be incremented when a breaking change is made to the application. We still have to define what is a breaking change in the context of this project.