Working with Release Packages

a release package contains information about all of the configuration items (for example, documentation, test plans, services, and so on) associated with a change and links to the release that is deploying the change typically, a may have already linked to a release, or created a request for release in the following illustration, the change record is linked to a standalone release, which contains all of the configuration items associated with the change the release is, in turn, linked to a release package which inherits all of the configuration items that are included in the change relationship between change, release, and release package for a standalone release the can decide to stagger the change between multiple releases (for example, master and phase releases) by creating multiple release packages for a single change for example, a change that involves a major software upgrade can be staggered among master and phase releases, each consisting of a release package that contains the configuration items and services that are affected at each phase of the release depending on the type of change and its scope, a release may or may not have a release package a single change record can have one or more release packages indirectly associated with it from the releases for example, if the change involves updating specific software on all the employees machines, the change might be rolled out in phases by location or by organization in such an instance, release packages are created for each phase of the release in the following illustration, the change record is linked to multiple releases each release is in turn linked to a different release package the links only those configuration items to the release record and release package that will be included in the actual release relationship between change, release, and release package for phased releases depending on the type of change and its scope, a release may or may not have a release package a single change record can have one or more releases associated with it for example, if the change involves updating specific software on all the employees machines, you may want to roll out the change in phases by location or by organization, and you can create releases for each phase creating a release package for a release when you are creating a release package from the release, the release id is already linked to the release package sign in to as a open the release workspace open the release record for which to create a release package from the release package tab, select new the new release package window opens enter information into the fields field name description name a title for this release package description a description of the release package status the release status pending if you need to do identify more items for the release package or you are still working on it implemented the release package is ready team the team responsible for the package owner the package owner change optional the change record id to be implemented and linked to this release package release the release id is automatically entered select save repeat to add other release packages to the release adding configuration items to a release package after you create a release package for a release and associate a change to it, link those configuration items that are part of the release package to the release package record sign in to as a open the release package workspace the list of release packages is displayed open a release package the release package form opens from the ci tab, select link select the appropriate configuration item record and click select repeat to add configuration item records to the release package select save