mirrors/apparmor
1
0
Fork 0
mirror of https://gitlab.com/apparmor/apparmor.git synced 2025-03-04 08:24:42 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update ReleaseProcess

John Johansen 2024-02-05 22:30:34 +00:00
parent a0bbade40a
commit 6e088b1fdf
1 changed files with 6 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
ReleaseProcess.md

@ -118,17 +118,12 @@ Milestones in launchpad are used both for attaching releases to, as well as for
* Choose to add the release
* add a link called "GPG signatures for gitlab artifacts" paste in link to GPG signature page generated in step 9
9. Sign the gitlab tarball (this differs slightly from the tarball above see ( https://gitlab.com/apparmor/apparmor/issues/37)
1. From apparmor-release utils use, sign-gitlab-artifacts.sh in the wiki directory
2. add the file to the wiki, push to gitlab
3. add link in gitlab release
4. Manual process - AVOID - cleanup move else where
5. Download the gitlab tarball
6. Sign the tarball with the apparmor signing key: `gpg --detach-sig --armor -u apparmor@lists.ubuntu.com TARBALL`
7. 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?
- \[sbeattie\]: followup: created a wiki page like so https://gitlab.com/apparmor/apparmor/-/wikis/3.1.1_Signatures
- **FIXME** This should be scripted.
1. These instructions assume you have a clone of the wiki and release tools in the same dir
2. cd into git clone of wiki
3. git pull (or fetch, followed by rebase)
4. run ../apparmor-release-utils/sign-gitlab-artifacts.sh VERSION (eg. VERSION == 3.1.7)
5. git push
6. Edit git release to add new "GPG signatures for gitlab artifacts" use link reported by sign-gitlab-artifacts.sh
10. \[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)
11. Create a new release from the milestone: https://launchpad.net/apparmor/+milestone/X.Y.Z/+addrelease - Once a release has been created in launchpad, files can be uploaded to it
12. Upload the tarball and detached gpg signature to the launchpad page: https://launchpad.net/apparmor/X.Y/X.Y.Z/+adddownloadfile (where X.Y is the series and X.Y.Z is the specific version) - The **Description** field should just be **AppArmor X.Y.Z**