From 3ba40eba4af2540ff9bac1bd9c8878e3a80f8a5e Mon Sep 17 00:00:00 2001 From: Kamalesh Babulal Date: Tue, 15 Apr 2025 21:54:45 +0530 Subject: [PATCH] doc/release: add step to push to release branch Update the release process documentation to include the missing step for pushing to the newly created release branch. Renumber subsequent steps to reflect the correct order. Suggested-by: Tom Hromatka Signed-off-by: Kamalesh Babulal Signed-off-by: Tom Hromatka TJH: Added "If this is a new..." text --- doc/internal/release-github.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/internal/release-github.md b/doc/internal/release-github.md index ac0d5018..ab077df4 100644 --- a/doc/internal/release-github.md +++ b/doc/internal/release-github.md @@ -74,14 +74,18 @@ release. # git push vX.Y.Z -#### 16. Create a new GitHub release using the associated tag and upload the following files +#### 16. If this is a new major/minor release, push the release branch to the main GitHub repository + + # git push release-X.Y + +#### 17. Create a new GitHub release using the associated tag and upload the following files * libcgroup-X.Y.Z.tar.gz * libcgroup-X.Y.Z.tar.gz.asc * libcgroup-X.Y.Z.tar.gz.SHA256SUM * libcgroup-X.Y.Z.tar.gz.SHA256SUM.asc -#### 17. Update the GitHub release notes for older releases which are now unsupported +#### 18. Update the GitHub release notes for older releases which are now unsupported The following Markdown text is suggested at the top of the release note, see old GitHub releases for examples. -- 2.47.3