Version Guidelines

Any major revisions that refactor large pieces of the code base or introduce breaking changes into the framework or methodology will cause a major version number change. For example 1. to 2.

Any major additions to the code will increment the secondary version number. For example 1.1 to 1.2. This can go on as long as breaking changes and large refactors are not included, such that the secondary version number reaches multiple digits, ex: 1.12 or 1.14.

Any change that is released to fix bugs or make minor revisions to the code will only include the two digit year followed by the two digit month (1.1.16.4 for April 2016). If multiple releases occur in the same month, then the day of the month can be added in addition, for example 1.1.16.4.15.