Update versions to reflect the actual state, we forgot about this in our last urgent release

This commit is contained in:
Jan Wagner 2024-07-23 14:54:06 +02:00 committed by Lorenz Kästle
parent 86053441b6
commit fffd13afda

View file

@ -2,7 +2,7 @@ Releasing a New Monitoring Plugins Version
==========================================
Throughout this document, it is assumed that the current Monitoring
Plugins version is 2.3.4, and that we're about to publish version 2.4.
Plugins version is 2.3.5, and that we're about to publish version 2.4.
It is also assumed that the official repository on GitHub is tracked
using the remote name `monitoring-plugins` (rather than `origin`).
@ -11,14 +11,14 @@ Before you start
- Check Github Actions status.
- Update local Git repository to the current `master` tip. For a
maintenance release (e.g., version 2.3.4), update to the current
maintenance release (e.g., version 2.3.6), update to the current
`maint-2.3` tip, instead.
Prepare and commit files
------------------------
- Update `configure.ac` and `NP-VERSION-GEN` with new version.
- Update `NEWS` from `git log --reverse v2.3.4..` output, and specify
- Update `NEWS` from `git log --reverse v2.3.5..` output, and specify
the release version/date.
- Update `AUTHORS` if there are new team members.
- Update `THANKS.in` using `tools/update-thanks`.
@ -93,6 +93,6 @@ Announce new release
If you want to mention the number of contributors in the announcement:
git shortlog -s v2.3.4..v2.4 | wc -l
git shortlog -s v2.3.5..v2.4 | wc -l
<!-- vim:set filetype=markdown textwidth=72: -->