To be clear, this blog post will focus on Stat specific to Release Management and not the song.
What’s Important? There are several key items that are important to know for Release Management:
Assigning Code to Releases: Associating or tagging an archive set with a specific release is as simple as assigning a value into the “Release” field dropdown menu while creating a new archive set.
Example of a Release Assigned Archive Set: Below is an example of assigning an archive set to a release during creation:
Hint: If you forgot to associate the release label with the code set, you can open the archive set and assign it at anytime. Provided you do not change any of the included objects within the code set, it should not affect any approvals obtained or information relevant for auditing.
Example of a Release Specific Migration:
If you are doing a Release, or Mass Migration, within Stat, you may not have a specific archive set opened. In that case you can go to the Stat main menu bar and select Migration Mgmt > Mass Migration
For a release specific migration, you would select the drop-down menu and select the Release Label you associated your code with:
The only thing to do next would be to select the “Migrate” button!
For more information, see Mass Migrating Objects on page 179 of the current Stat Users guide.
We will discuss rolling back at the release level using the Stat Release Recovery Wizard in our next blog.
Thanks for taking the time to read this blog and I hope you found it informative.
William R. Hart
Quest | Pre-Sales
Office +1 727 787 7374