Versions Compared

Old Version 6

changes.mady.by.user Halina Tomaszewska

Saved on

compared with

New Version Current

changes.mady.by.user Halina Tomaszewska

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


The goal is to release one day after the sprint ends.


Hotfix procedure for Partner Portal / SonWin Classic can be found HERE



Version history

DateVersionAction byAction
29. July 20251.0HALTOEstablished
13. August 20251.1HALTOAdded step 8 - Hand over to support
25. September1.2

HANAG

HALTO

Added step 20 - Managing releases through a round-robin system

Minor change to step 19 - Release notes PDF is sent as a attachment 



IDStepAdditional infoResponsible

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
3Technical release notes are added, if relevant. 
DEV
4The fixed version field is then 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.

    		• PO
    5Client release notes are translated.
    		PM/Danish speaking person
    6Hand 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
    7QA is conducting the regression test, bugs are fixed if any and
    retested.Release
    re-tested.
    		QA/DEV
    8Hand over to support 
    		DEV/QA
    9User manual is updated.
    		PO
    10User manual is translated.
    		PM/Danish speaking person
    11Client 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).
  • The release note is uploaded to Partner Portal.
    •  

    We will follow the same manual process as Zynergy.

    EG Partners Release Notes

    		PM/PO
    12Release notes PDF is uploaded to EG Zynergy Partners.
    		DEV
    13User manual PDF is uploaded to EG Zynergy Partners.
    		DEV
    14"About" information is updated with the version etc. to reflect the released version
    		DEV
    15Code is pushed to Staging
    		DEV
    16QA is performing a test - on functionality that does not require access to SonWin DB.
    		QA
    17SonWin related testing in Staging must be performed by Nordic team members due to GDPR
    		Nordic team members
    18Code is pushed to production.
    		DEV

    19

    		Information is sent to grid companies about a new release by email with
    a link to PDF.
    release notes PDF document as attachment.
    		PM/PO

    20

    The release process is managed through a round-robin system to ensure equitable distribution and smooth workflow

     
    		DEV
    IDStepAdditional infoResponsible1

    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/POWhen epic/story/bug is set to done, the client release note is written.DEV/POTechnical release note is added, if relevant.DEVThe fixed version field is then set to the release name.POClient release note is translated.PM/Danish speaking personHand 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.DEVQA is conducting the regression test, bugs are fixed if any and retested.QA/DEVRelease 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.