mir/apparmor
2
0
Fork 0
mirror of https://gitlab.com/apparmor/apparmor synced 2025-08-30 22:05:27 +00:00
Code Issues Releases Wiki Activity

Update ReleaseProcess: tweak formatting, ask question on gitlab tarball signing.

Steve Beattie
2022-08-27 08:28:26 +00:00
parent 97c65f8a45
commit 4b234995be
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
ReleaseProcess.md

@@ -123,10 +123,11 @@ as well as for bug targeting. To create a new milestone:
- Note that tags can be deleted and re-added if testing the generated release shows a critical bug that needs to be fixed before release.
7. GIT: push tag to the repository `git push <upstream repo> +<tag>`
8. Sign the gitlab tarball (this differs slightly from the tarball above see (https://gitlab.com/apparmor/apparmor/issues/37)
8.1 Download the gitlab tarball
8.2 Sign the tarball with the apparmor signing key: `gpg --detach-sig --armor -u apparmor@lists.ubuntu.com TARBALL`
8.3. Verify that the signature was done correctly: `gpg --verify TARBALL.asc`
1. Download the gitlab tarball
2. Sign the tarball with the apparmor signing key: `gpg --detach-sig --armor -u apparmor@lists.ubuntu.com TARBALL`
3. Verify that the signature was done correctly: `gpg --verify TARBALL.asc`
- The AppArmor signing key has the fingerprint **3ECD CBA5 FB34 D254 961C C53F 6689 E64E 3D36 64BB**
- [sbeattie]: **XXX** where should the signatures be uploaded / attached?
9. \[Optional\] upload packages based on the release to the appropriate apparmor-dev ppa: https://launchpad.net/~apparmor-dev/+archive/apparmor-X.Y (where X.Y is the series version)
10. Create a new release from the milestone: https://launchpad.net/apparmor/+milestone/X.Y.Z/+addrelease