Short note: version and release management

Version and release management is the part of configuration management that keeps track of the different versions of a system and controls how versions are delivered to customers.

Terms

• Version: an instance of a system that is functionally different in some way from other instances (for example v2.1).
• Variant: a version that has the same functionality as others but differs in non-functional ways, for example one built for a different operating system or hardware.
• Release: a version that is distributed to customers.

Version management covers:

• Version identification: a clear naming scheme, such as version numbering (1.0, 1.1, 2.0), attribute-based identification (date, platform, customer), or change-oriented identification.
• Storage: storing all versions efficiently, usually as one full version plus deltas (differences).
• Tracking the relationship between versions in a version tree, and controlling check-in and check-out of components.

Release management covers:

• Deciding when to release, based on technical quality, competition, marketing needs, platform changes and customer change requests.
• Preparing the release: executable code, configuration files, data files, installation program, documentation (user manual, release notes) and packaging.
• Distributing it and recording exactly which component versions, compiler and libraries were used, so the release can be re-created later.

Example: a mobile app's v3.2 release includes the new APK, database migration scripts and release notes, while v3.1.4 remains supported for older devices.