Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Fetching contributors…

Cannot retrieve contributors at this time

file 71 lines (45 sloc) 1.861 kb
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71
This is a pre-release checklist for the maintainer.

 * is there any "FIX" in: ChangeLog, INSTALL, Announce?

 * Is .htaccess installed?
 * rm -f /etc/munin/plugins/*
      Does munin-node-configure -d show any autoconf errors?
      Does munin-node-configure --debug run nicely or do we get perl errors?

 * Update plugins/plugins.history.in:

   1. cd plugins

   2. Figure out which r the previous tag was at and do this (r910 was
1.3.2 and r1234 is head)
      svn --verbose log -r910:1234 | fgrep node.d | grep -w A |
         cut -d/ -f 4- | sed 's/^node\.d\.//'

   3. Check if the listed plugins are still present (or moved):

      svn --verbose log -r910:1234 | fgrep node.d | grep -w A |
          cut -d/ -f 4- | sed s'/(.*//' | xargs ls -ld >/dev/null


# Git release

  We follow the workflow documented at
  http://nvie.com/posts/a-successful-git-branching-model/

  The tag used here is "2.0.1", exchange this with a current version.

 * Create release branch from "devel"

   git checkout -b release-2.0.1 devel

 * Update ChangeLog

   $EDITOR Changelog
   git commit -m 'Update changelog for release' -- ChangeLog

 * Merge release branch to master

   git checkout master
   git merge --no-ff release-2.0.1

   (handle any conflicts, and "git commit" the result)

 * Tag on master

   git tag -a -s -m 'Release 2.0.1' 2.0.1 master

 * Merge the release branch back to devel

  git checkout devel
  git merge --no-ff release-2.0.1

# Make tarball from tag

  git checkout 2.0.1
  make tar

# Propaganda

 * Broadcast the good news:
   1. make a sha256sum : sha256sum munin-version.tar.gz > munin-version.tar.gz.sha256sum
      and sign it using gpg.
   2. Upload the tar.gz on sourceforge.net
   3. Create a news on sf annoucing it
   4. Update our front page
   5. Create a new release on freshmeat.net
   6. Send an email to the ML
Something went wrong with that request. Please try again.