When does a software release product require a version number? [135]

Because software may be further developed and subsequently updated after the original version is released, all revised software should be released with a new version number. It is recommended that all releases follow a version numbering scheme. Although the approach to version numbering can vary, revised software releases can be grouped into three general categories: major revision, minor revision, and patch.

• Major Revision: This is a numbered software release that includes significant code changes. The changes may: render the software incompatible with previous release dependencies such as operating systems or code reference libraries; include changes to the underlying development framework (for example, Java version or Spring Framework version); result in output that differs from or is incompatible with output from prior versions; or indicate a substantial deviation from a previous major release through a combination of minor releases. Major releases require a new approval record in the IPDS.
• Minor Revision: This is a numbered software release that includes less significant code changes such as those that include the addition of new features, bug fixes, or incorporate other minor changes, but the software largely (or wholly) remains backward-compatible with the previous software major release.
• Patch: This is a numbered software release that includes backward-compatible bug fixes only.