@@ -133,6 +133,19 @@ The end-to-end process consists on the following stages:
Details of the patch release lifecycle can be found on the [patch release documentation], including the
[patch release runbook for GitLab engineers] and the [patch release runbook for release managers].
### Patch release information dashboard
GitLab team members can view the [internal Grafana dashboard "Release Information"](https://dashboards.gitlab.net/d/delivery-release_info/delivery3a-release-information?orgId=1) for the following information about the active patch release:
* Active patch release versions (stable version + 2 backport versions)
* Upcoming patch release date
* Current status of the patch release
* Open: Bug fixes and MRs associated with security issues labelled `security-target` are expected to be included in the next patch release.
* Warning: Signals that teams should get bug and security fixes ready to merge.
* Closed: Default branch MRs have been merged, no further bug or security fixes will be included.
The metrics used to display this information are updated automatically throughout the [patch release process](#patch-release-process).
## Security releases
The [security release processes](/handbook/engineering/releases/security-releases/#security-release-process) are used to prepare and publish packages containing vulnerability fixes. For more details about the release overview and the release processes, see the [security release](/handbook/engineering/releases/security-releases/) page.
