Releasing a New Monitoring Plugins Version

Throughout this document, it is assumed that the current Monitoring Plugins version is 2.2.1, and that we're about to publish version 2.3.

Before you start

Check Travis CI status.
Update local Git repository to the current master tip. For a maintenance release (e.g., version 2.2.2), update to the current maint-2.2 tip, instead.

Update NEWS from git log --reverse v2.2.1.. output, and specify the release version/date.
Update configure.ac and NP-VERSION-GEN with new version.
Update AUTHORS if there are new team members.
Update THANKS.in:

tools/update-thanks
Commit the results:

git commit configure.ac NP-VERSION-GEN AUTHORS THANKS.in

git tag -a v2.3 -m v2.3

git push monitoring-plugins master
git push monitoring-plugins v2.3

Only necessary when creating a feature release.

git checkout -b maint-2.3 v2.3
git push -u monitoring-plugins maint-2.3

rm -rf /tmp/plugins
git archive --prefix=tmp/plugins/ v2.3 | (cd /; tar -xf -)

cd /tmp/plugins
tools/setup
./configure
make dist

scp monitoring-plugins-2.3.tar.gz \
    plugins@orwell.monitoring-plugins.org:web/download/

ssh plugins@orwell.monitoring-plugins.org \
    '(cd web/download; \
      $HOME/bin/create-checksum monitoring-plugins-2.3.tar.gz)'

In the site.git repository,
- create web/input/news/release-2-3.md,
- update the plugins_release version in web/macros.py, and
git add web/input/news/release-2-3.md git commit web/input/news/release-2-3.md web/macros.py git push origin master
Post an announcement on (at least) the following mailing lists:
- announce@monitoring-plugins.org
- help@monitoring-plugins.org (set Reply-To: to this one)
Ask the social media department to announce the release on Twitter :-)

If you want to mention the number of contributors in the announcement:

git shortlog -s v2.2.1..v2.3 | wc -l