summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Moore <paul@paul-moore.com>2021-04-28 19:55:33 -0400
committerPaul Moore <paul@paul-moore.com>2021-04-28 21:09:36 -0400
commite1224fd090da1fef6090b11264290fa53375eeb6 (patch)
treebcec180c1245cd714468a94502641982012c0306
parentc56a00fe173a7dd5a8326431ae28863ce432bbc1 (diff)
downloadlibseccomp-e1224fd090da1fef6090b11264290fa53375eeb6.tar.gz
docs: update RELEASE_PROCESS.md to push the release tag as late as possible
In order to help reduce confusion by those who closely follow the libseccomp repository on GitHub, push new release tags as late in the release process as possible. Reviewed-by: Tom Hromatka <tom.hromatka@oracle.com> Signed-off-by: Paul Moore <paul@paul-moore.com>
-rw-r--r--doc/admin/RELEASE_PROCESS.md11
1 files changed, 7 insertions, 4 deletions
diff --git a/doc/admin/RELEASE_PROCESS.md b/doc/admin/RELEASE_PROCESS.md
index 5f09ce1..9cc55eb 100644
--- a/doc/admin/RELEASE_PROCESS.md
+++ b/doc/admin/RELEASE_PROCESS.md
@@ -62,10 +62,9 @@ release.
#### 11. Update the version number in configure.ac AC_INIT(...) macro
-#### 12. Tag the release in the repository with a signed tag
+#### 12. Tag the release in the local repository with a signed tag
# git tag -s -m "version X.Y.Z" vX.Y.Z
- # git push <repo> vX.Y.Z
#### 13. Build final release tarball
@@ -89,14 +88,18 @@ release.
# gpg --armor --detach-sign libseccomp-X.Y.Z.tar.gz
# gpg --clearsign libseccomp-X.Y.Z.tar.gz.SHA256SUM
-#### 17. Create a new GitHub release using the associated tag; added the relevant section from the CHANGELOG file, and upload the following files
+#### 17. Push the release tag to the main GitHub repository
+
+ # git push <repo> vX.Y.Z
+
+#### 18. Create a new GitHub release using the associated tag; added the relevant section from the CHANGELOG file, and upload the following files
* libseccomp-X.Y.Z.tar.gz
* libseccomp-X.Y.Z.tar.gz.asc
* libseccomp-X.Y.Z.tar.gz.SHA256SUM
* libseccomp-X.Y.Z.tar.gz.SHA256SUM.asc
-#### 18. Update the GitHub release notes for older releases which are now unsupported
+#### 19. 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.