Release is a process that involves the replication of approved and baselined objects (refer to the Approval and Baselining Standard), and their migration between environments, or their issue to end-users.
This may involve producing physical copies of the objects, e.g. a paper copy of the design, or the migration of objects from one environment to another, e.g. copying baselined objects from development into production.
The aim of release control is to ensure that only baselined objects are released in a complete and consistent form and that sufficient documentation is supplied to enable effective installation and usage.
Where released objects require processing, i.e. populating with data, etc., then release control must ensure that adequate documentation is produced to enable this processing to progress without any problems.
The release of “Draft” objects does not require formal control; however, recipients must be aware when such a release has taken place.
A Release Coordinator shall be appointed who has the following responsibilities:
• Preparing and/or constructing a release: The Release Coordinator shall construct the release using the appropriate configuration records (refer to the Build Management Standard).
• Ensuring that all released objects have been approved and baselined (refer to the Approval and Baselining Standard)
• Generating release documentation.
• Performing the release activity.
• Maintaining necessary release records.
Staff requiring copies of objects shall do so by making a formal request to the Release Coordinator.
The Release Coordinator shall prepare a release using the appropriate configuration records (refer to the Configuration Management Standard)
Where a release is constructed using two or more objects (i.e. a software release), then the Release Coordinator shall make use of the configuration records and the appropriate build files (refer to the Build Management Standard) to construct the release.
Where a release requires installation by the recipient, then the Release Coordinator shall ensure that all necessary user documentation and installation instructions are issued.
Where a release corrects one or more defects or contains enhancements to a previous release, then the Release Coordinator shall ensure that a release document is prepared and issued.
Where acknowledgement of receipt is required from the recipient, then the Release Coordinator shall ensure that a release acknowledgement form is prepared and issued.
Releases shall be assigned a unique reference and shall be logged in a release log.
The release instructions shall define the following:
• Back-up procedure for existing objects. This shall define how to archive or destroy old objects. For paper releases this may specify the need to return previously issued objects to the Release Coordinator.
• Tasks to install the new release.
• Recovery procedure in the event of a failed release.
The release document shall define the following:
• List of errors fixed.
• List of new enhancements.
• List of outstanding errors.
• Release contents: this must identify the individual objects being released and their version number.
In certain circumstances, e.g. the issue of an important contractual document, a release acknowledgement form shall be issued with the release requesting acknowledgement from the recipient.
The release acknowledgement form shall contain the following:
• Release identifier: a unique reference for the release.
• Date of release.
• Recipient’s name and signature.
The Release Coordinator shall construct a release package. The release package may contain the following items:
• Released objects: Where necessary, objects shall be packaged to protect them while in transit.
• Release instructions.
• Release Document.
• Release Acknowledgement Form.
Once the release package is complete, the Release Coordinator shall archive a copy of the complete package and update the release log with the following information:
• Package reference.
• Release description.
• Date of release.
• Recipients.
• Date of acknowledgement.
• Location of archive.
The Release Coordinator shall obtain authorization, e.g. from the Software Development Manager, before issuing the release package.