Software Release Management
Release Management ensures provides a controlled approach to the product / service / systrem evolution from the prespective of functionaslity (i.e. what the systen can do?), quality (i.e. the number of defects that prevent the end-user from doing their daily assignments) and more.
-
Release Manager Responsibilities
Resolution incidents cause and to prevent their recurrence.
-
Process Input
-
Release Policy
-
Release items from project management and ITSM change management
-
Approval from senior management
-
The history of the affected configuration items from the configuration database
-
-
Process Output
-
Detailed documenation about the history of each release and release decisions taken.
-
Updated configuration items.
-
Updated release items from project management and change management
-
-
Performance Indicator(s) (PI)
-
Number of releases per year
-
Number of change items per release
-
Number of helpdesk issues per release (new issues because of the release)
-
New issues vs. fixed issues ratio per release
-
The Release Management system serves also as an indicator of the product / service / systrem quality.
A release is a group of new or modified CIs which have been validated for installation in the live environment. The functional and technical specifications of a version are defined in the corresponding CR Releases may be classified, according to their impact on the IT infrastructure, as:
-
Major releases: representing a significant roll-out of hardware and software and which introduce important modifications to the functionality, technical characteristics, etc.
-
Minor releases: these usually entail the correction of one or more specific errors and are often modifications that implement documented emergency solutions correctly.
-
Emergency releases: modifications repairing a known error quickly
The universally accepted system is:
-
Major releases: 1.0, 2.0, etc.
-
Minor releases: 1.1, 1.2, 1.3, etc.
-
Emergency releases: 1.1.1, 1.1.2, e
