This article outlines the Freeze and Released stages of a release.
On the planned date, the responsible development team member moves the release page from the In Progress status to the Freeze status. A notification about this is sent to the #Activity stream, where all product owners whose areas of responsibility included tickets in the current release are informed.
From this moment until the planned pre-release date, new feature development is halted:
- Teams finalize, test, and move tickets that were already in progress to the Done status.
- Product owners assign a new release to tickets remaining in the Ready to go status or move them back to the backlog.
- Product owners compile the results of tickets in the Done status into a list of changes for their respective areas of responsibility.
- The responsible development team member edits the release page and incorporates the lists of changes provided by the product owners.
On the pre-release date, all changes are migrated from the development environment to the test environment. Until the actual release date, teams verify the functionality of the updated components and fix any identified bugs.
On the release date, the system is updated for end users, i.e., all changes are imported from the test environment into the production environment. After this, the responsible team member clicks the Release button on the release page, and the status changes to Released.
A released page may look like this:
Planned release dates and the history of update releases can be tracked on the release management main page.
Found a typo? Select it and press Ctrl+Enter to send us feedback