UG:CT2 Releases
From UG
Contents |
About
Release notes are attached into 0002170: [Management] (ongoing)
Release policy
1) Emergency.
Reasons: Urgent bug (UB, example: 3610) or Urgent change (UC:3622). In this case we apply chnage to tag of latest prod release. No code merge required. Code changes are minimal and staging would take max 1-2 days. Could be done on a short notice.
2) Regular.
Normally includes list of DQ tasks (commited to trunk) and project tasks (commited to 1 or more branches). Code merge required. 4 days staging required. We should have release dates set in advance. We should create such releases not too often. Ideally once in 4-8 weeks.
Related Mantis fields
- RelDate - release date, example: 06/15
- RNum - release version number, example: 2.24.0
- RYear - release year, example: 2012
- ph:
- Stg - tasks in staging before release
- Rel - tasks after being released
2012
June
06/15
- regular release (first GM Split release + DQ)
- number: 2.24.0
Media:CT2 Release Notes 2 24 0.pdf
06/23
- release type: emergency
- number:2.24.2
- tasks:
- 0003622: Bug: Cannot post new PI to into 2011 CT # 313212 & warning message is received
- 0003610: Sales Invoices with VAT charges, add VAT Rate % in PDF Body next to VAT Amount for ALL UK and FR sales invoices generated
06/TBD
- release type: regular
- first DR/KPI release + DQ
- number:
- tasks:
- TBD
