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 2019-09-16 14:19:21 +00:00
parent 5fd81f9b53
commit 8c1ab4c869
1 changed files with 15 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
ReleaseProcess.md

@ -120,14 +120,20 @@ as well as for bug targeting. To create a new milestone:
6. Tag the release with `make tag` in the toplevel of an up to date checked out tree, to ensure consistently named tags. This does the equivalent of `bzr tag apparmor_VERSION` (e.g. `bzr tag apparmor_2.6.0`).
- 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. \[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)
9. Create a new release from the milestone: https://launchpad.net/apparmor/+milestone/X.Y.Z/+addrelease
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`
- The AppArmor signing key has the fingerprint **3ECD CBA5 FB34 D254 961C C53F 6689 E64E 3D36 64BB**
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
- Once a release has been created in launchpad, files can be uploaded to it
10. 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)
11. 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**
11. [Branch the release](ReleaseProcess#Branching_Userspace_Trees) (For major releases only)
12. [Branch the release](ReleaseProcess#Branching_Userspace_Trees) (For major releases only)
- For point releases (2.6.x) a new branch is unnecessary, as only stable patches are being applied. The tag is sufficient to identify the release points.
12. Update wiki
13. Update wiki
- Update the release notes. There are two separate entries for release notes:
1. A stub entry on the [release notes](AppArmor_versions) page.
- The release note stub should have its release date updated to the current date
@ -138,7 +144,7 @@ as well as for bug targeting. To create a new milestone:
- Update current release information on the [main page](Main_Page#Userspace)
- if major release or point release for the most recent major release, update **Current stable release**
- if point release for an older release series, update **Prior supported release**
13. Mirror to kernel.org (require kernel.org account)
1. Mirror to kernel.org (require kernel.org account)
- Mirror release tarball
- If major release create a release directory in **/pub/linux/security/apparmor/**.
- minor releases use the major release directory, but have the point release as part of their name
@ -149,9 +155,9 @@ as well as for bug targeting. To create a new milestone:
- **/pub/scm/linux/security/apparmor/**
- Make sure any additional kernel patches are synced to the apparmor kernel tree
- **/pub/scm/linux/kernel/git/jj/apparmor-dev.git/**
14. Send announcement of the release to the apparmor mailing list **apparmor@lists.ubuntu.com**
15. Make a copy of the announcement on the launchpad page at https://launchpad.net/apparmor/+announce
16. Go through bugs targeted to the milestone https://bugs.launchpad.net/apparmor/+milestone/X.Y.Z and either close them or move them to a different milestone if they were not fixed by this release
15. Send announcement of the release to the apparmor mailing list **apparmor@lists.ubuntu.com**
16. Make a copy of the announcement on the launchpad page at https://launchpad.net/apparmor/+announce
17. Go through bugs targeted to the milestone https://bugs.launchpad.net/apparmor/+milestone/X.Y.Z and either close them or move them to a different milestone if they were not fixed by this release
> ??? Register a new series in lp - when should this be done? Before
> files can be uploaded to it, but can be after branch is created