summaryrefslogtreecommitdiff
path: root/doc
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:07:10 -0400
commit5822e50c2920ce597d038077dea4a0eedf193f86 (patch)
tree0979a014bae9177afba3bcda8035eac06ff55374 /doc
parentde60727c86e5946521b17763edb5ec344fc43da4 (diff)
downloadlibseccomp-5822e50c2920ce597d038077dea4a0eedf193f86.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>
Diffstat (limited to 'doc')
-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.