# Release

> [HTML Version](release-finish.html)

This article outlines the **Freeze **and **Released **stages of a [release](release.md).

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](360014162972.md), where all product owners whose [areas of responsibility](release-settings.md#responsibility-area) included tickets in the current release are informed.

From this moment until the planned pre-release date, new feature development is halted:

- [Teams](release-settings.md#dev-team) finalize, test, and move tickets that were already [in progress](ticket-life-cycle.md#development) 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](ticket-life-cycle.md#backlog).

- Product owners compile the results of tickets in the [Done](ticket-life-cycle.md#ticket-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](release-settings.md#test-companies). 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:

**(release-1.png)**

- On the **Main** tab, you can view release information such as the dates associated with the release, the list of changes, and so on.

- The **Tickets** tab displays a list of tasks completed as part of the release.

- The **Requests, RFC, Problems**, and **CMDB** tabs are displayed if records from these apps have been linked to tickets included in the release. Items whose work or completion is affected by the implemented functionality are shown here.

- The **History** tab records changes made to the release page, such as status changes, field edits, and so on.

Planned release dates and the history of update releases can be tracked on the [release management main page](release-main-page.md).