Denotes technical contributions required from tech advisors to the release post process

For discussions, processes, and guidelines about GitLab releases.

Issues that are a stretch goal for delivering in the current milestone. If these issues are not done in the current release, they will strongly be considered for the next release.

Issues scoped for Tanukey Beta release

Issues scoped for the Tanukey Experiment release

A backwards-incompatible change that will need to be made with the next major release. See https://docs.gitlab.com/ee/development/contributing/index.html#breaking-changes

A tracking issue for a critical security release

Issues about per repository and global deploy keys, part of the Release stage of the DevOps lifecycle

A security issue which has been validated, broken down, planned/designed, developed and is waiting for a security release to be deployed. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382

[DEPRECATED] should use devops::deploy. Issues for the Release stage of the DevOps lifecycle (e.g. CD, Release Automation, Pages, Review apps)

Issues for Feature Management, part of the Release stage of the DevOps lifecycle

Issue was discovered in release pipeline.

[DEPRECATED] should use group::environments now. Issues belonging to the Release stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#progressive-delivery-group

MRs or releases that contain potential breaking changes. These releases should be monitored when deployed.

Issues relating to release management (new GitLab release, Ruby gems, etc).

All issues and MRs related to the mobile publishing capability within devops:release

Issues which are particularly important to be released in the specified milestone. This should only be set by the responsible PM.

Applies to epics, issues or MRs that should be highlighted on a Product Operations release page.