aboutsummaryrefslogtreecommitdiff
path: root/doc/RELEASING
diff options
context:
space:
mode:
authorGravatar Ton Voon <tonvoon@users.sourceforge.net> 2005-03-04 21:03:43 +0000
committerGravatar Ton Voon <tonvoon@users.sourceforge.net> 2005-03-04 21:03:43 +0000
commit40670c97c9f4f92c4697b7ed7f8c55e3811b25c9 (patch)
tree9c3ee7cc4a92ebf719506c521e2fe1aa3d49d1cc /doc/RELEASING
parent0074c80300e51c9c13fa9039ed4a1803d6e56f4e (diff)
downloadmonitoring-plugins-40670c97c9f4f92c4697b7ed7f8c55e3811b25c9.tar.gz
Notes on branching
git-svn-id: https://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/trunk@1143 f882894a-f735-0410-b71e-b25c423dba1c
Diffstat (limited to 'doc/RELEASING')
-rw-r--r--doc/RELEASING7
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/RELEASING b/doc/RELEASING
index 4f61c301..0f708f39 100644
--- a/doc/RELEASING
+++ b/doc/RELEASING
@@ -11,6 +11,9 @@ 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?
checkout new version:
cd /tmp
@@ -30,7 +33,7 @@ put file
SF -> Submit News about release.
Get URL to news item
-SF -> Admin -> File Release System
+SF -> Admin -> File Releases
Add a release to nagiosplug and create a file release
name: 1.4-alpha2. Commit
Step 1: Add release notes pointing to news item
@@ -40,5 +43,5 @@ Step 4: Send notice
Send email to nagiosplug-help, nagios-announce
-Change version number in configure.in and package.def
+Change to next version number in configure.in and package.def