Versioning Standards

Release Branches

Release branches will follow the naming convention:

[MODULE]_[MAJOR RELEASE]_[MINOR RELEASE]

Major Release:
Major releases signify significant changes to a module. Developers may perform a major release if there have been substantial improvements to the component. Developers must perform a major release whenever the new release is not at least interface-compatible the previous release.

Minor Release:
Minor releases signify enhancements to a component that do not necessitate a major release. Developers may perform a minor release if the release is at least external-interface-compatible with the previous release. In other words, whenever a client depends upon at most the external interface of a component with a given minor release, it will work with all subsequent minor releases within that major release.

An example for the legalleads module would be: WORKFLOW_1_0

Build Tags

Build tags represent a periodic build that was taken for whatever release. It will follow the naming convention:

[moduleabbrev][major release][minor release]_[build number]

An example for the workflow module would be: wf10_b1