aboutsummaryrefslogtreecommitdiffstats
path: root/doc/versioning.md
diff options
context:
space:
mode:
authorRiku Isokoski <riksu9000@gmail.com>2021-09-22 12:03:41 +0300
committerRiku Isokoski <riksu9000@gmail.com>2021-09-22 12:03:41 +0300
commitb2100908373f76660fcfb5f3c454eb69a38ca4ef (patch)
tree090a52c4e10646a0d7a9383920452342b4898f4c /doc/versioning.md
parentb31b2425f8afd5022173852f5a78592b37104c39 (diff)
parent1c3c3c8db919c703bbd3f1be4ce9c6833237ea6f (diff)
Merge branch 'develop' into detect_full_charge
Diffstat (limited to 'doc/versioning.md')
-rw-r--r--doc/versioning.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/versioning.md b/doc/versioning.md
index b08af714..48e05043 100644
--- a/doc/versioning.md
+++ b/doc/versioning.md
@@ -3,4 +3,4 @@ The versioning of this project is based on [Semantic versionning](https://semver
- 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 functionning 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. 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