> For the complete documentation index, see [llms.txt](https://docs.runway.team/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.runway.team/using-runway/release-steps/release-overview.md).

# Release overview

From the **Release overview** page, you can make edits to release parameters and status, as well as view a number of useful high-level metrics related to the release. Some metrics are evergreen through the life of the release, and others only appear after a release has been completed.

Many of these statistics will display a “Change” value which shows how the particular metric is tracking compared to the historical average for that metric across previous releases. This helps your team understand how certain key metrics are trending over time, and whether things are moving in a positive or negative direction.

At the top of the Release overview page, you'll find important dates for the release, as well as a button to **Edit release** and update release status.

## Actions from 'Edit release' button

### Edit release

Modify basic parameters about your release here:

* **Release version** (required) - Enter the planned version number of your next release. Runway will determine whether it's a major, minor, or point release based on [semantic versioning rules](https://semver.org/).
* **Release pilot** - Choose a specific team member to act as release pilot for this release. If no selection is made, Runway will automatically assign a release pilot from a rotation of team members who are [eligible to be release pilots](/using-runway/organization-settings/team.md#groups) for this app.
* **Target kickoff date** - Specify a target date for when you plan to kick off this release.
  * For release branch teams, Runway considers a release kicked off when a release branch is detected or [created by Runway](/automations/types-of-automations.md#release-cycle).
  * For static branch teams, Runway considers a release kicked off when code is detected past the last release tag, or when [Runway promotes code](/automations/types-of-automations.md#release-cycle) from your development branch to your release branch.
* **Target submit date** - Specify a target date for when you plan to submit this release to the app store for review.
* **Target release date** - Specify a target date for when you plan to release this app update to end users.

### Complete release

This action will mark the release as completed in Runway.

* The release will be moved to the 'Completed' section of releases.
* The next up release will then become the active release.

{% hint style="success" %}
This can be used in cases where there was no automated feedback that the release completed naturally (*e.g.* complete status from app stores, or a completed CI workflow run for OTA apps).
{% endhint %}

### Un-complete release

This action will mark the release as not completed in Runway.

* The release will be moved to the 'Active' section of releases.
* The release will become the active release.

{% hint style="info" %}
If you choose to **un-complete** a release, you must confirm that there is no active release with the same version on the **production track** in Google Play Console. If such a release exists, Runway will automatically re-complete the release upon the next refresh.
{% endhint %}

### Skip release

This action will mark the release as skipped.

* The release will be moved to the 'Completed' section of releases
* The next up release will then become the active release.
* When choosing to skip a release, Runway presents the following options: 
  * **Roll forward metadata changes from this release:** This will ensure that any metadata changes ("What's new" text, etc.) made to this release are applied to the next active release.
  * **Pull active app submission:** This will ensure that the subsequent release is not blocked from submission due to this skipped release. This option will only be present if Runway detects that this release is currently in a submitted state in an app store.   

{% hint style="info" %}
Typically, the 'Skip' option is used when a release hasn't actually been published to the app store or otherwise has not been pushed live to users, but the team wants to maintain a record that it existed. All releases except those marked as 'Completed' can be skipped.
{% endhint %}

{% hint style="warning" %}
If Runway's [Tag releases at the end of the release cycle](/automations/types-of-automations.md#tag-releases-at-the-end-of-the-release-cycle) automation is enabled, it will not run for skipped releases. 
{% endhint %}

### Un-skip release

This action will mark the release as active.

* The release will be moved to the 'Active' section of releases.
* The release will become the active release.

{% hint style="info" %}
Not all automations will re-run if the release is un-skipped. Only recurring automations, along with any one-time automations that hadn't already run, will re-run.
{% endhint %}

### Delete release

This action will remove the record of this release from Runway's list of planned app versions.

## Release overview metrics

### Product sprint

In the Product sprint section of the Release overview page, you’ll see a number of product-related statistics about your release surfaced, including:

* Items of work completed
* Number of fixes
* Fix percentage (percetange of completed work items that were fixes)
* Fixes approved / rejected
* Number of CI builds
* Number of App Store / Play Console builds
* Time spent “Waiting for review” (iOS only)
* Time spent “In review” (iOS only)
* Number of product teams that contributed to the release
  * Based on the number of completed tickets in a release, and the team associated with each completed ticket. A bar graph will also display teams that have completed the most tickets in the release, in descending order.

![](https://lh5.googleusercontent.com/6mzU20ez1Sawar6Al948Hik7EM_cw624nvfsWCfHZhLt-JfXIaT29YhaOzbc4PzK9x3kZhbpm1O2XQ04MNaCmuJ91loI7_2yjhEWXdJLZzLETL2VJtL3CFeSIUFqCRk8hdMIq2_A)

### Code

The Code section of release overview shows metrics related to CI/CD builds and code for the release. Here, you’ll find statistics such as:

* Build workflow success rate
* Number of commits
* Average build time
* Number of code contributors
  * A bar graph will also display individuals that have contributed the most commits to the release, in descending order.
* Number of files changed
  * Includes a list of top changed files, ranked by the volume of code that was changed in those files.

![](https://lh5.googleusercontent.com/8ann8JqVSPyjGafrc5bckcb47heYG2y4CDn1vmMpUtp4S9nQYjjbpUtOLEjJY1uEUL5DOc7D1-_lzJPisLkYssLfw1rwTF6HWapsy7QtWGS2tw0yHplktMxbuphpLgOcoER-k92J)

![](https://lh6.googleusercontent.com/bEqvwDvAePTAEA2CPp8ccmv_yBrrgXHb2ByPkAZxAaVe_lFZ6R5i1uT2XXtppnUVX8aWN8c4TnD8WKMbl5Z43VaQPYpM2BzpLKzDgLdl4v-nlJ8EGFX50fnnq45kFfJXZX1v7l2Z)