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 2023-07-11 14:47:35 +00:00
parent 0c3e88c607
commit c8ba13c807
1 changed files with 7 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
ReleaseProcess.md

@ -123,7 +123,13 @@ 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.
- **FIXME** currently make tag causes a tag to be signed with the individual's gpg key; we should change this to be gpg signed by the project key.
7. GIT: push tag to the repository `git push <upstream repo> +<tag>`
8. create the gitlab release. Deployments->Releases. New Release. Choose just pushed tag. Add Link to release notes and blank GPG signatures wiki page. Partial copy of Head of release notes into release notes section. XXXX clean this up
8. create the gitlab release. Deployments->Releases. New Release. Choose just pushed tag.<br>
1. copy the head of the release notes into the Description section
2. Add a Link to release notes called "Full release notes"
3. Create Release
4. you will come back to add the GPG signatures after step 9 Sign the gitlab tarball
* 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 <release> in the wiki directory
2. add the file to the wiki, push to gitlab