The goal is to release one day after the sprint ends.
| 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 note is 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 retested |
| . | QA/DEV | ||
| 8 | User manual is updated. | PO | |
| 9 | User manual is translated. | PM/Danish speaking person | |
| 10 | Client release notes are created as PDF using the same template as Zynergy. |
| We will connect with Technical Writer Moa once she is back from vacation to learn how Zynergy is handling the release process |
| . | PM/PO | ||
| 11 | Release notes PDF is uploaded to EG Zynergy Partners. | DEV | |
| 12 | User manual PDF is uploaded to EG Zynergy Partners. | DEV | |
| 13 | "About" information is updated with the version etc. to reflect the released version | DEV | |
| 14 | Code is pushed to Staging | DEV | |
| 15 | QA is performing a test - on functionality that does not require access to SonWin DB. | QA | |
| 16 | SonWin related testing in Staging must be performed by Nordic team members due to GDPR | Nordic team memebers | |
| 17 | Code is pushed to production. | More detailed information TBD | DEV |
| 18 | Information is sent to grid companies about a new release by email with a link to PDF |
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 |