From 3c32c841a8a1089240c8bcd1d7a47f4f32a34b9f Mon Sep 17 00:00:00 2001 From: Paul Meyer <49727155+katexochen@users.noreply.github.com> Date: Tue, 12 Mar 2024 17:01:58 +0100 Subject: [PATCH] dev-docs: improve patch release documentation Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com> --- dev-docs/release.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/dev-docs/release.md b/dev-docs/release.md index 997cc8bbb..e32170000 100644 --- a/dev-docs/release.md +++ b/dev-docs/release.md @@ -34,6 +34,12 @@ ## Patch +> [!NOTE] +> We do backports by applying backport labels (`backport release/v`) to PRs that should be backported. +> The backport then happens automatically by the backport action on merge. If you label a PR that was already +> merged, the backport action can be triggered by adding a `/backport` comment. Ensure the backport PR has +> the proper label to gets listed in the release notes. + 1. Ensure all needed PRs were backported to the current release branch, and all backport PRs were merged. 2. Export the release you want to make: @@ -48,6 +54,7 @@ ```sh git switch "release/${REL_VER%.*}" + git pull ``` 4. Create a new temporary branch for the relese: