The goal is to release one day after the sprint ends.
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). During the sprint bugs may be added.
- When epic/story/bug is set to done, the fixed version field is set to the release name.
- This is also when the client release note for each item is added.
- As well as technical release note, when relevant.
- The client release note description is translated.
- 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.
- QA is conducting the regression test, bugs are fixed if any and retested.
- Release notes are exported from Confluence page as PDFcreated 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).
- The release note is uploaded to Partner Portal.
- "About" information is updated with the version etc. to reflect the released version
- Code is pushed to Staging
- QA is performing a test - on functionality that does not require access to SonWin DB.
- SonWin related testing in Staging must be performed by Nordic team members due to GDPR
- Code is pushed to production.
- Information is sent to grid companies about a new release by email with a link to PDF.