Skip to content

Commit bd5ba3f

Browse files
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 <tom.hromatka@oracle.com> Signed-off-by: Kamalesh Babulal <kamalesh.babulal@oracle.com>
1 parent 565c13c commit bd5ba3f

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

doc/internal/release-github.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,14 +74,18 @@ release.
7474

7575
# git push <repo> vX.Y.Z
7676

77-
#### 16. Create a new GitHub release using the associated tag and upload the following files
77+
#### 16. Push the release branch to the main GitHub repository
78+
79+
# git push <repo> release-X.Y
80+
81+
#### 17. Create a new GitHub release using the associated tag and upload the following files
7882

7983
* libcgroup-X.Y.Z.tar.gz
8084
* libcgroup-X.Y.Z.tar.gz.asc
8185
* libcgroup-X.Y.Z.tar.gz.SHA256SUM
8286
* libcgroup-X.Y.Z.tar.gz.SHA256SUM.asc
8387

84-
#### 17. Update the GitHub release notes for older releases which are now unsupported
88+
#### 18. Update the GitHub release notes for older releases which are now unsupported
8589

8690
The following Markdown text is suggested at the top of the release note, see old GitHub releases for examples.
8791

0 commit comments

Comments
 (0)