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 2022-08-23 20:08:15 +00:00
parent 124cb84119
commit 50442cbcee
1 changed files with 107 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

107
ReleaseProcess.md

@ -221,3 +221,110 @@ To do this, the following steps should be taken:
8. Modify the bzr REPOURL location in the top level Makefile to match the new branch; make tarball needs this to be correct for subsequent releases off of the branch,
9. edit common/Version to adjust in preparation for the XX+1 release with something like 2.XX.90 (git doesn't like '~' in tags, so versioning like 2.XY~pre1 are a bad idea)
10. send email to list **\[administrative\] AppArmor 2.XX branch created**, with branch url and note about needing nominations
# Release Notes
# Release Announcements
1. Email
2. launchpad
3. gitlab
4. twitter
5. webpage (apparmor.net)
The webpage announcement uses the the basic outline provided by the release notes.
1. Update your local website repo
```
git checkout master
git fetch origin
git rebase
```
If you don't have a local copy you can make a clone doing (this assumes your gitlab access keys are setup.
```
git clone git@gitlab.com:apparmor/apparmor.net.git
cd apparmor.net
```
2. Branch release announcement from updated master
For a 3.0.7 release you could do
```
git checkout -b 3.0.7
```
3. copy the previous release notes header to a new markdown file in ```content/news```. The header is very important the release announcement will not show up with out it.
Eg.
```
cp content/news/release-3.0.6.md content/news/release-3.0.7.md
```
Then edit the file to remove the previous release notes. The date in the file is the date of the release, not the day of the web announcement. This can be found on the full release notes page in the wiki.
Eg. the 3.0.6 header would change from
```
---
title: AppArmor 3.0.6 released
date: 2022-08-01
---
```
to
```
---
title: AppArmor 3.0.7 released
date: 2022-08-09
---
```
4. Copy the mark down from the release notes.
Go to the release notes page, hit the edit button select the text copy, and then ```Cancel``` the edit.
In your editor paste the release note into the web announcement file, after the header (look at other release announcements for examples).
Rmove the date header and ```#introduction``` from the top of the release notes. Save the file.
5. Add the release file and commit
```
git add content/news/release-3.0.7.md
git commit -s
```
Write a commit message (see git log for examples).
6. push the branch to your fork of the website project. The website is set up to reject any pushes to it, this must go to your own fork.
Eg.
```
git push jj 3.0.7
```
7. Go to the gitlab [website](https://gitlab.com/apparmor/apparmor.net) and create a merge request.
8. Approve the merge request and merge it.
9. Delete your local branch and remote branch
```
git checkout master
git branch -D 3.0.7
git push -d jj 3.0.7
```