Decision Rules – Sprint vs Release » History » Version 1
Redmine Admin, 12/24/2025 03:55 PM
| 1 | 1 | Redmine Admin | h1. Decision Rules – Sprint vs Release |
|---|---|---|---|
| 2 | |||
| 3 | This table defines how Sprint Versions and Release Versions must be used. |
||
| 4 | |||
| 5 | {{toc}} |
||
| 6 | |||
| 7 | h2. Decision Table |
||
| 8 | |||
| 9 | |_. Situation |_. Sprint Version |_. Release Version | |
||
| 10 | | Normal development | Temporary | Not used | |
||
| 11 | | Sprint completion | Cleared | Not used | |
||
| 12 | | Planned release | Not used | Permanent | |
||
| 13 | | Hotfix | Not used | Patch release | |
||
| 14 | | Rollback | Not used | New patch | |
||
| 15 | |||
| 16 | --- |
||
| 17 | |||
| 18 | h2. Governing Rules |
||
| 19 | |||
| 20 | 1. Sprint is an execution container |
||
| 21 | 2. Release is a business contract |
||
| 22 | 3. Sprint and Release must never coexist on one issue |
||
| 23 | 4. History is preserved via custom fields |
||
| 24 | 5. Never rewrite history to look clean |