1This is a pre-release checklist for the maintainer.
2
3 * is there any "FIX" in: ChangeLog, INSTALL, Announce?
4
5 * Is .htaccess installed?
6 * rm -f /etc/munin/plugins/*
7      Does munin-node-configure -d show any autoconf errors?
8      Does munin-node-configure --debug run nicely or do we get perl errors?
9
10 * Update plugins/plugins.history.in:
11
12   1. cd plugins
13
14   2. Figure out which r the previous tag was at and do this (r910 was
15	  1.3.2 and r1234 is head)
16      svn --verbose log -r910:1234 | fgrep node.d | grep -w A |
17         cut -d/ -f 4- | sed 's/^node\.d\.//'
18
19   3. Check if the listed plugins are still present (or moved):
20
21      svn --verbose log -r910:1234 | fgrep node.d | grep -w A |
22          cut -d/ -f 4- | sed s'/(.*//' | xargs ls -ld >/dev/null
23
24
25# Git release
26
27  The tag used here is "2.0.1", exchange this with a current version.
28
29 * Update ChangeLog
30
31   new="2.0.1"; old=$(git describe --abbrev=0)
32   header=$(printf '\nmunin-%s, %s\n%s' "$new" "$(date +%Y-%m-%d)" "$(sed -n 4,14p ChangeLog)")
33   shortlog=$(git log --pretty=short --no-merges "${old}.." | git shortlog)
34   printf "%s\n\n%s\n\n" "$header" "$shortlog" | sed -i "1r /dev/stdin" ChangeLog
35
36 * Commit the updated changelog and tag this release
37
38   git commit -m "$new" -- ChangeLog
39   git tag -s "$new" -m "$new"
40
41# Make tarball from tag
42
43  git checkout 2.0.1
44  make tar
45  OR
46  make tar-signed
47
48# Propaganda
49
50 * Broadcast the good news:
51   1. Upload the release tar and signature:
52      make tar-upload
53   2. Update our website
54   3. Send an email to the ML
55   4. Update the version in the topic of the IRC channel
56