Results (
Indonesian) 2:
[Copy]Copied!
Release packaging
Build management procedures, methodologies, tools and checklists should be applied to ensure that the release
package is built in a standard and controlled way in line with the solution design defined in the service design
package. As a release package progresses towards production it may need to be rebuilt. For example, if a newer version
needs to be incorporated quickly to fix errors; or if the documentation needs to be updated.
The key activities to build a release package are:
Assemble and integrate the release components in a controlled manner
Create the build and release documentation including: build, installation and test plans, procedures and
scripts
Monitor and check the quality of the release and how to recognise and react to problems
The automated or manual processes and procedures required to distribute, deploy and install the release into
the target environment (or remove it as necessary)
Procedures to back out release units or remediate a change should a release fail
Procedures for tracking and managing software licences
Install and verify the release package
Baseline the contents of the release package
Send a notification to relevant parties that the release package is available for installation and use
If testing of a release package is successful, the release and the contents of the release package are placed under
the control of configuration management, baselined and verified against the release design and release package
definition.
From this point all changes to the release package are managed through change management, e.g. to fix an error in
testing.
If at any step the testing of a release package does not complete successfully, reassessment and rescheduling of the
release is managed through change management.
Being translated, please wait..