Version Numbering Policy - Washington-University/HCPpipelines GitHub Wiki
Starting with the first officially released version of this project, v3.4.0
, the version numbering scheme is intended to be as follows: v<major>.<minor>.<bug-fix>
.
So:
- Going from version
v3.x.x
tov4.0.0
would imply some "major" functionality change or addition. - Going from version
v3.4.x
tov3.5.0
would imply some "minor" functionality change or addition. - Going from version
v3.4.x
tov3.4.x+1
would imply no functionality change other than a bug fix to makev3.4.x
what it "should have been".
For example, version v3.4.1
is a bug-fix release that changes no script or tool functionality whatsoever, but instead fixes a "bug" with where the external documentation (installation information, usage notes, FAQ, etc.) is located.
See Semantic Versioning 2.0.0 for further guidelines.