diff --git a/ReleaseProcess.md b/ReleaseProcess.md index 2f981bb..50f2f70 100644 --- a/ReleaseProcess.md +++ b/ReleaseProcess.md @@ -123,7 +123,8 @@ 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 +` -8. Sign the gitlab tarball (this differs slightly from the tarball above see (https://gitlab.com/apparmor/apparmor/issues/37) +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 +9. Sign the gitlab tarball (this differs slightly from the tarball above see (https://gitlab.com/apparmor/apparmor/issues/37) 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` @@ -132,14 +133,14 @@ as well as for bug targeting. To create a new milestone: - [sbeattie]: followup: created a wiki page like so - **FIXME** This should be scripted. -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 +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 -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) +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** -12. [Branch the release](ReleaseProcess#Branching_Userspace_Trees) (For major releases only) +13. [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. -13. Update wiki +14. 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 @@ -151,7 +152,7 @@ as well as for bug targeting. To create a new milestone: - 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** - update [Kernel](Kernel_Feature_Matrix) and [Userspace](Userspace_Feature_Matrix) feature matrixes -14. Mirror to kernel.org (require kernel.org account) +15. 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 @@ -162,10 +163,10 @@ 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/** -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 -18. Go through ["Fix Committed" bugs](https://bugs.launchpad.net/apparmor/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=FIXCOMMITTED). For each of them: if the committed fix made it into this release, change status to Fix Released* +16. Send announcement of the release to the apparmor mailing list **apparmor@lists.ubuntu.com** +17. Make a copy of the announcement on the launchpad page at https://launchpad.net/apparmor/+announce +18. 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 +19. Go through ["Fix Committed" bugs](https://bugs.launchpad.net/apparmor/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=FIXCOMMITTED). For each of them: if the committed fix made it into this release, change status to Fix Released* > ??? 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