summaryrefslogtreecommitdiff
path: root/doc/versioning.md
diff options
context:
space:
mode:
authorJF <jf@codingfield.com>2021-09-26 09:16:55 (GMT)
committerGitea <gitea@fake.local>2021-09-26 09:16:55 (GMT)
commit6652ec6f71967f4a8eea1f159aa500a1a21a5902 (patch)
treecdbbf9afede8ea74258867ba41905a3fe0d784f4 /doc/versioning.md
parent6c3d6fb2575888e582e7ef3004a0bc3bf6c588b6 (diff)
parentd03db14129b4f8cc2e691dd6f9e8d8d1ed52b7a1 (diff)
Merge branch 'develop' of JF/PineTime into master
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 b08af71..48e0504 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