aboutsummaryrefslogtreecommitdiff
path: root/doc/RELEASING
diff options
context:
space:
mode:
authorGravatar Ton Voon <tonvoon@users.sourceforge.net> 2005-09-19 13:46:04 +0000
committerGravatar Ton Voon <tonvoon@users.sourceforge.net> 2005-09-19 13:46:04 +0000
commitc46ee2e8352444883061c413183db399468a889f (patch)
tree8f62b9f18b0bb80bb40b739e8517cfd7a83b9884 /doc/RELEASING
parent291a30d024b2ba500515c9759522d234aa9cd8e6 (diff)
downloadmonitoring-plugins-c46ee2e8352444883061c413183db399468a889f.tar.gz
Reminders for news item and tag format
git-svn-id: https://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/trunk@1226 f882894a-f735-0410-b71e-b25c423dba1c
Diffstat (limited to 'doc/RELEASING')
-rw-r--r--doc/RELEASING16
1 files changed, 7 insertions, 9 deletions
diff --git a/doc/RELEASING b/doc/RELEASING
index 0f708f39..c1c9d06e 100644
--- a/doc/RELEASING
+++ b/doc/RELEASING
@@ -9,11 +9,8 @@ Update BUGS file, if this is a major release
Run cvs2cl.pl
commit new ChangeLog
-Check configure.in with right version
-cvs tag r1_4-alpha2
-If a main release (eg, non alpha/beta), branch here:
-cvs tab -b r1_4-patches
-Consider the SF snapshot branches - should you remove any other branches?
+Check configure.in and package.def with right version
+cvs tag r1_4_1
checkout new version:
cd /tmp
@@ -31,17 +28,18 @@ cd /incoming
put file
SF -> Submit News about release.
+List major changes.
+List all people on team involved.
+Add acknowledgement to contributors
Get URL to news item
SF -> Admin -> File Releases
Add a release to nagiosplug and create a file release
-name: 1.4-alpha2. Commit
+Name: 1.4-alpha2. Create release
Step 1: Add release notes pointing to news item
Step 2: add file
Step 3: *.tar.gz, Platform Independent, Source .gz
Step 4: Send notice
-Send email to nagiosplug-help, nagios-announce
-
-Change to next version number in configure.in and package.def
+Send email to nagiosplug-help, nagios-announce with the news text