Software Release Management

Basic Concept:
 A release is a group of new or modified
CIs which have been validated for
installation in the live environment.
 Releases may be classified according to
their impact on the IT infrastructure, as:
Types Of Releases
Major Releases:
 Representing a significant roll-out of hardware and
software and which introduce important modifications
to the functionally , technical characteristics etc.

Minor Release:
These usually entail the correction of one or more
specific errors and are often modification that
implement documented emergency solution correctly.
Types Of Releases
Emergency Release:
 Modifications repairing a known error correctly.
 As there may be multiple versions it is worth defining a
reference or code unambiguously identifying them .
 The universal accepted systems are:

• Major releases: 1.0 ,2.0 , etc.

• Minor Releases: 1.1 , 1.2 , 1.3 , etc.
• Emergency releases: 1.1.1 , 1.1.2 , etc.
 During its life-cycle a release may go through various
states:
• Developing .
• Testing .
• Live .
• Archived.
 New versions can be rolled out in different ways and it
is the responsibility of Change Management to decide
the more appropriate way of proceeding.
 The most common options include:
• Delta release: Only modified components are tested
and installed. This option has the advantage of greatest
simplicity, but it entails the risk that problem or
incompatibilities may arise in the live environment.
• Full release: All the affected components are
distributed ,whether they have been modified or not.
Although this option obviously involve more work ,
provided the relevant tests have been done , it is less
likely that incidents ill occur after installation.
 Package of releases : Change management may
opt to distribute different packages of releases in a
synchronized way . This offers greater stability in the IT
environment . In some cases this option is unavoidable
due to incompatibilities between a new version and
previously installed hardware or software . Consider a
migration to a new operating system requiring more
advanced hardware and / or new versions of office
automation programs .
Release Management Process
 The main activities involved in Release
Management may be summarized as:
• Establishing a planning policy for the implementation of
new versions.
• Developing new versions or buying them from third
parties.
• Testing new versions in an environment that simulate
the environment as closely as possible.
• Validating the new versions.
• Implementing new versions in the live environment .
• Informing and training customers and users about the
functionality of the newly released version.
Release Management Processes
 Planning:
It is crucial to establish a general framework
for the launch of new version. This must set out the
working methods. This is especially important for small
or emergency releases , as in the case of large releases
specific plans taking into account the specific features of
each case will be drawn up .
Development:
Release management is responsible for
designing and building new versions. This development
work is sometimes done in-house , but in many cases
require the involvement of external service providers.
Release Management Processes
In this latter case , the role of Release Management is to ensure
that the hardware or software package or packages offered
meet the specification . Release Management will also be
responsible for the complete configuration process necessary.

This development must include , if necessary or advisable , all the

installation scripts needed for the deployment of the version. These
scripts must take into account aspects such as :
• Automatic data back-ups .
• Any update that need to be made to the associated databases .
• Installation of new version on different systems or at diff sites.
• Creating the logs of the installation process .
Release Management Processes
 Validation:
A well planned test protocol is absolutely essential if
a new version is to be released onto the live system
with reasonable certainty of success .
Test should not be limited to performing purely
technical validation (checking for the absence of
errors), rather functional tests with real users must be
conducted to ensure that the version meets the set
requirements and is reasonably usable ( there will
always be degree of resistance to change among users
and this should be taken into account ) .
Release Management Processes
 Validation :
Release Management will be responsible for final validation of
the version before proceeding with its installation. If the version is
not accepted it will be returned to Release Management for the
evaluation.

 Implementation :
The moment of trust has arrived , the distribution of the
new version, or rollout :
 Complete and synchronized : A complete rollout
takes place simultaneously on all sites .
Release Management Processes
 Fragmented :
Either in space or time . For example , the new version
is released to different work groups or the functionality
offered is progressively increased . After the release ,
Release Management must be informed in a timely way
by the Service Desk of any comments , complaints ,
incidents , etc . That the new system may have
produced.
Thanks for Listening
ANY QUESTIONS ?