Release Package Overview

Release packages are portions of IT or Service Infrastructure normally built, deployed, tested, and released together. Release packages define the set of changes to be deployed and drive the deployment processes.

One or more development change requests and deployment units are associated with each release package. Deployment tasks are associated with release packages and are executed as part of the release package workflow.

Release packages can be dependent or independent. Dependent release packages are associated with application releases and are part of the release train hierarchy. Independent release packages are standalone entities.

Dependent release packages are associated with application releases. This ensures that the changes included and deployed as part of the release packages have followed the full workflow and approvals needed for the release train and application release of which they are a part.

Using dependent release packages ensures that complete release scheduling and planning processes are followed before deployment to any environments.

Independent release packages enable you to perform hotfix and emergency releases outside of the scope of a release train and application releases.

For example, you may need to do a data fix to a field that had an incorrect date format applied during an upgrade, and rather than initiate a formal release train and application release for this, you could expedite the change by creating an independent release package and sending it through the simpler workflow to deployment.

Independent release packages enable you to deploy urgent or low-impact changes into production quickly while still leveraging the visibility, automated deployment, and audit trail capabilities of Serena Release Control.

Associations with release packages include the following: