diff options
| author | JF <jf@codingfield.com> | 2020-07-27 21:25:00 +0200 |
|---|---|---|
| committer | JF <jf@codingfield.com> | 2020-07-27 21:25:00 +0200 |
| commit | 71e8c320b03ea6ee302baa0035e08dc7fb657174 (patch) | |
| tree | fbece0d6c1e0980c8d17237aec4a1d43c8afe3e4 /doc/versioning.md | |
| parent | c04d22ee0ac20c64a389c10d98f1c2417d788e13 (diff) | |
| parent | 8c77c8631de753a4c32bc7c79a22a1452b37f3f6 (diff) | |
Merge branch 'develop' of git.proxmox3:JF/PineTime into develop
# Conflicts:
# README.md
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 00000000..b08af714 --- /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 |