Actions
Decision Rules – Sprint vs Release¶
This table defines how Sprint Versions and Release Versions must be used.
- Table of contents
- Decision Rules – Sprint vs Release
Decision Table¶
| Situation | Sprint Version | Release Version |
|---|---|---|
| Normal development | Temporary | Not used |
| Sprint completion | Cleared | Not used |
| Planned release | Not used | Permanent |
| Hotfix | Not used | Patch release |
| Rollback | Not used | New patch |
Governing Rules¶
1. Sprint is an execution container
2. Release is a business contract
3. Sprint and Release must never coexist on one issue
4. History is preserved via custom fields
5. Never rewrite history to look clean
Updated by Redmine Admin 4 months ago · 1 revisions