diff options
| author | JF <jf@codingfield.com> | 2020-09-26 15:09:24 (GMT) |
|---|---|---|
| committer | Gitea <gitea@fake.local> | 2020-09-26 15:09:24 (GMT) |
| commit | b6a910e52ed98b662e6586f45cfe9c6997f8f158 (patch) | |
| tree | d74185cbf682cde40e5de5bfa2f620ae201565a9 /doc/versioning.md | |
| parent | be05997272b7b1d1b25b122c8162ac6f4c1c12a2 (diff) | |
| parent | 3e612e79ba82bac69258094d468c996c41b29612 (diff) | |
Merge branch 'develop' of JF/PineTime into master
Diffstat (limited to 'doc/versioning.md')
| -rw-r--r-- | doc/versioning.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/versioning.md b/doc/versioning.md new file mode 100644 index 0000000..b08af71 --- /dev/null +++ b/doc/versioning.md @@ -0,0 +1,6 @@ +# Versioning +The versioning of this project is based on [Semantic versionning](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 functionning firmware suited for the final user.
\ No newline at end of file |