Issues for improving security release workflow

Security implementation issues with this label will be automatically considered for the next scheduled security release. The evaluation runs around the top of each hour.

Items under consideration for the next few releases

Issues relating to the Slack slash commands feature released in 8.15: https://docs.gitlab.com/ee/user/project/integrations/slack_slash_commands.html

this label is used by automated product operations release pages

Issues that need to be scheduled for a future release

Related to style standards for documentation, UI text (per Pajamas Content guide), or the Release Post. Typically involving the Technical Writing Style Committee.

Related to tools, process, standards for doc/UI/Release Post content testing, including linting. Also use more-specific labels like ~vale or ~markdownlint, if applicable. Typically involving the Technical Writing Test Automation Committee.

GitLab security releases. This label should only be added for (critical) security root/meta issues. Do not add this label to individual security issues and/or merge requests.

This is a security issue that is ready to be deployed but awaiting a security release

Issues that are ready for development but are not yet active (or have an associated release). https://about.gitlab.com/handbook/product-development-flow/