# Release

## Pre-Stage

Unknown

## Stage Entry Requirement

* Stories in stage does not exceed WIP

## Stage Workflow

* Unknown

## Stage Exit Requirement

* Unknown

## Post-Stage

Unknown

## Concepts

* Releases
* ProjectName
* Version
* Summary
* DeployInstructions
* RollbackInstructions
* TicketNumber
* ReleasePackagePath
* Notes
* Note
* User
* Date
* Note
* Deployments
* Deployment
* Environment
* DateRequested
* DateScheduled
* DateCompleted
* RequesterUser
* SupporterUser
* ApproverUser
* ValidatorUser
* ReleaserUser

Maybe, the deployment users can be a little more flexible by just including a list of associated users and assigning various deployment roles to the users (Approver, Supporter, Validator…). Then the deployment roles won’t be hard coded like they are and hard to add and remove roles.

Release Status

* New
* Accepted
* Rejected
* Exception
* Authorized
* Scheduled
* Implemented
* Closed

Release Policy defines the release workflow for an environment or project

* Commit
* Build
* Test
* Analyze
* Gate Release Candidate&#x20;
* Accepted
* Rejected
* Exception
* Publish Release Candidate
* Authorize Deployment
* Dev
* QA
* Owner
* Release Manager
* Schedule
* Deploy
* Confirm Deployment
* Dev Verify
* QA Validate
* Owner Accept
* Release Manager
* Close
* Rollback

Quick-Add

* Project
* Release
* Deployment
* Note
