Numbering - pyhrf/pyhrf GitHub Wiki
Warning : this is a draft version of the document. Do not consider the following accurate.
pyhrf version number try to respect the SemVer convention:
MAJOR.MINOR.PATCH
with:
- MAJOR = API. Any big changes of the core which leads to modifications of the API which can breaks external applications (e.g. graphical user interface)
- MINOR = improvements. Adding new algorithms, new functionalities which are backwards-compatible
- PATCH = Bug fixes. Cleanup, bad results,… (backwards-compatible)
One exception should be the 1.0.0 version which should indicate first stable version of pyhrf.
If you need to identify a pre-release or identify the commit append it to the version number: e.g. 1.2.3-beta+git.a2c4f67
For further info check the Semantic Versioning Specification (SemVer)