文档介绍：Release Management
1
Goal – Primary Objective
To take an holistic (Overall) view of a Change to an IT service and ensure that all aspects of a release, both technical and non-technical are considered together
2
Why Release Management
Manage large or critical hardware roll-outs
Manage major software roll-outs
Bundling or batching related sets of changes
Control the release of authorised CIs into the supported environment
Release Policy
A release policy document should be produced to clarify the roles and responsibilities for Release Management. There may be one document anisation or an umbrella set of guidelines and specific details for each supported service
3
Responsibilities of Release Management
Release Policy
Release Planning
Develop or purchase software
Build / configure release
Fit for purpose testing
Release acceptance
Roll out planning
Communication preparation & training
Distribution & installation
Configuration Management Database (CMDB)
and
Definitive Software Library (DSL)
Controlled Test Environment
Live Environment
RELEASE MANAGEMENT
Development
Environment
4
Terminology
Definitive Software Library (DSL)
Definitive Software Library – where ALL authorised versions of software are stored
and protected. A Physical library or storage repository where master copies of software
versions are kept. This one logical store may consist of one or more physical software
libraries or file stores.
Definitive Hardware Store (DHS)
Definitive Hardware Store – An area set aside for the secure storage of definitive hardware spares.
Types of Release
- Delta, Full and Package
Definitions
Release: a collection of authorised Changes to an IT Service
Release Unit: the portion of the IT infrastructure that is normally released together
Roll-out: deliver, install mission an integrated set of new or changed CIs across logical or physical parts of anisation
5
Types of Release
Delta
Only those CI’s that have actually changed since last release
are in