The goal is to release one day after the sprint ends.
Hotfix procedure for Partner Portal / SonWin Classic can be found HERE
Version history
| Date | Version | Action by | Action |
|---|---|---|---|
| 29. July 2025 | 1.0 | HALTO | Established |
| 13. August 2025 | 1.1 | HALTO | Added step 8 - Hand over to support |
| ID | Step | Additional info | Responsible |
|---|---|---|---|
1 | When a sprint starts, we decide what will go into the release. This is done by adding a label to epic/story/bug with a given release name (e.g. S17). Note: During the sprint bugs may be added. | PM/PO | |
2 | When epic/story/bug is set to done, the client release note is written for each ticket. | DEV/PO | |
| 3 | Technical release notes are added, if relevant. | DEV | |
| 4 | The fixed version field is then set to the release name. | PO | |
| 5 | Client release notes are translated. | PM/Danish speaking person | |
| 6 | Hand over to QA for regression testing is done three working days before sprint ends. | Sprint ends on a Tuesday, hand over is Wednesday (the week before) by the end of the day. | DEV |
| 7 | QA is conducting the regression test, bugs are fixed if any and re-tested. | QA/DEV | |
| 8 | Hand over to support | DEV/QA | |
| 9 | User manual is updated. | PO | |
| 10 | User manual is translated. | PM/Danish speaking person | |
| 11 | Client release notes are created as PDF using the same template as Zynergy. | We will follow the same manual process as Zynergy. | PM/PO |
| 12 | Release notes PDF is uploaded to EG Zynergy Partners. | DEV | |
| 13 | User manual PDF is uploaded to EG Zynergy Partners. | DEV | |
| 14 | "About" information is updated with the version etc. to reflect the released version | DEV | |
| 15 | Code is pushed to Staging | DEV | |
| 16 | QA is performing a test - on functionality that does not require access to SonWin DB. | QA | |
| 17 | SonWin related testing in Staging must be performed by Nordic team members due to GDPR | Nordic team memebers | |
| 18 | Code is pushed to production. | More detailed information TBD | DEV |
19 | Information is sent to grid companies about a new release by email with a link to PDF. | PM/PO | |
20 | The release process is managed through a round-robin system to ensure equitable distribution and smooth workflow | DEV |