The Release with Emergency lifecycle is used to make many changes to an application and release those changes as a group identified by a release number. That release is used as an initial point for the next development effort. In addition, this lifecycle is designed to handle any emergency (off hours) changes. The changes are made in the Emergency state as a branch. The branches are deployed to production for emergency purposes and the changes are merged with development code in the Development state.
The Release with Emergency lifecycle has the states: Development, Test, Release, View Snapshots, and Emergency. Changes are isolated in each state (except between Emergency and Product which share the same view) so that they do not affect the released application. Developers or Development Managers can use the Package Distribution UDP to generate a report that shows the packages that are in each state.
|
Copyright © 2013 CA.
All rights reserved.
|
|