---
title: "Short note: version and release management"
subject: "Software Engineering"
chapter: 10
key: "semester_5/software_engineering:version-release-management"
source: https://www.bctengineer.com/q/semester_5/software_engineering/version-release-management
site: BCT Engineering
---

# Short note: version and release management

Software Engineering · Chapter 10: Configuration Management

- Asked in: 2068 Chaitra, 2.5 marks; 2069 Chaitra, 3 marks; year not given, 3 marks (asked 2 times)
- Video: [SCM- (S/W VERSION & RELEASE MGMT.)](https://www.youtube.com/watch?v=nC3SZaFJITc) — Sunny Sall
- Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14
- Page: https://www.bctengineer.com/q/semester_5/software_engineering/version-release-management
- Whole chapter: https://www.bctengineer.com/md/semester_5/software_engineering/chapter-10

## Question

Write a short note on version and release management.

## Short answer

Version management identifies functionally different instances via numbering, delta storage, and version trees. Release management decides when to distribute a version, prepares executables, data files, installation programs and documentation, and records exact component versions to ensure reproducibility.

## Answer

**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.

## Check yourself

The answer's key points as multiple-choice questions, with the correct option and why.

1. What is a release?
   A. Any internal development copy
   B. A version distributed to customers
   C. A deleted version
   D. A test case
   Answer: B. A release is a version that is distributed to customers. (Key point: Version vs release)

2. How are versions usually stored efficiently?
   A. Full copy of every version
   B. Only the newest version
   C. Printed on paper
   D. One full version plus deltas (differences)
   Answer: D. Storing one full version plus deltas saves space. (Key point: Delta storage)

3. Why record the component versions, compiler and libraries used for a release?
   A. So the release can be re-created later
   B. To increase file size
   C. To reduce testing
   D. To hide changes
   Answer: A. Exact records let the same release be rebuilt later. (Key point: Release recording)