[monitoring-plugins] Update version in release docu
Jan Wagner
git at monitoring-plugins.org
Thu Jul 25 15:40:11 CEST 2024
Module: monitoring-plugins
Branch: master
Commit: 78f5d6b9ed62b1c7b5fcd523176a2c3f35f514b7
Author: Jan Wagner <waja at cyconet.org>
Date: Wed Jul 24 22:29:00 2024 +0200
URL: https://www.monitoring-plugins.org/repositories/monitoring-plugins/commit/?id=78f5d6b
Update version in release docu
---
doc/RELEASING.md | 30 +++++++++++++++---------------
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/doc/RELEASING.md b/doc/RELEASING.md
index cd2deae..e1f3bf7 100644
--- a/doc/RELEASING.md
+++ b/doc/RELEASING.md
@@ -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.5, and that we're about to publish version 2.4.
+Plugins version is 2.4.0, and that we're about to publish version 2.5.
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.6), update to the current
- `maint-2.3` tip, instead.
+ maintenance release (e.g., version 2.4.1), update to the current
+ `maint-2.4` tip, instead.
Prepare and commit files
------------------------
- Update `configure.ac` and `NP-VERSION-GEN` with new version.
-- Update `NEWS` from `git log --reverse v2.3.5..` output, and specify
+- Update `NEWS` from `git log --reverse v2.4.0..` output, and specify
the release version/date.
- Update `AUTHORS` if there are new team members.
- Update `THANKS.in` using `tools/update-thanks`.
@@ -29,27 +29,27 @@ Prepare and commit files
Create annotated tag
--------------------
- git tag -a -m 'Monitoring Plugins 2.4' v2.4
+ git tag -a -m 'Monitoring Plugins 2.5' v2.5
Push the code and tag to GitHub
-------------------------------
git push monitoring-plugins master
- git push monitoring-plugins v2.4
+ git push monitoring-plugins v2.5
Create new maintenance branch
-----------------------------
_Only necessary when creating a feature release._
- git checkout -b maint-2.4 v2.4
- git push -u monitoring-plugins maint-2.4
+ git checkout -b maint-2.5 v2.5
+ git push -u monitoring-plugins maint-2.5
Checkout new version
--------------------
rm -rf /tmp/plugins
- git archive --prefix=tmp/plugins/ v2.4 | (cd /; tar -xf -)
+ git archive --prefix=tmp/plugins/ v2.5 | (cd /; tar -xf -)
Build the tarball
-----------------
@@ -62,26 +62,26 @@ Build the tarball
Upload tarball to web site
--------------------------
- scp monitoring-plugins-2.4.tar.gz \
+ scp monitoring-plugins-2.5.tar.gz \
plugins at orwell.monitoring-plugins.org:web/download/
Generate SHA1 checksum file on web site
---------------------------------------
ssh plugins at orwell.monitoring-plugins.org \
- '(cd web/download; $HOME/bin/create-checksum monitoring-plugins-2.4.tar.gz)'
+ '(cd web/download; $HOME/bin/create-checksum monitoring-plugins-2.5.tar.gz)'
Announce new release
--------------------
- In the site.git repository:
- - Create `web/input/news/release-2-4.md`.
+ - Create `web/input/news/release-2.5.md`.
- Update the `plugins_release` version in `web/macros.py`.
- Commit and push the result:
- git add web/input/news/release-2-4.md
- git commit web/input/news/release-2-4.md web/macros.py
+ git add web/input/news/release-2.5.md
+ git commit web/input/news/release-2.5.md web/macros.py
git push origin master
- Post an announcement on (at least) the following mailing lists:
@@ -93,6 +93,6 @@ Announce new release
If you want to mention the number of contributors in the announcement:
- git shortlog -s v2.3.5..v2.4 | wc -l
+ git shortlog -s v2.4.0..v2.5 | wc -l
<!-- vim:set filetype=markdown textwidth=72: -->
More information about the Commits
mailing list