summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorTon Voon <tonvoon@users.sourceforge.net>2005-03-04 21:03:43 (GMT)
committerTon Voon <tonvoon@users.sourceforge.net>2005-03-04 21:03:43 (GMT)
commit40670c97c9f4f92c4697b7ed7f8c55e3811b25c9 (patch)
tree9c3ee7cc4a92ebf719506c521e2fe1aa3d49d1cc /doc
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')
-rw-r--r--doc/RELEASING7
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/RELEASING b/doc/RELEASING
index 4f61c30..0f708f3 100644
--- a/doc/RELEASING
+++ b/doc/RELEASING
@@ -11,6 +11,9 @@ commit new ChangeLog
11 11
12Check configure.in with right version 12Check configure.in with right version
13cvs tag r1_4-alpha2 13cvs tag r1_4-alpha2
14If a main release (eg, non alpha/beta), branch here:
15cvs tab -b r1_4-patches
16Consider the SF snapshot branches - should you remove any other branches?
14 17
15checkout new version: 18checkout new version:
16cd /tmp 19cd /tmp
@@ -30,7 +33,7 @@ put file
30SF -> Submit News about release. 33SF -> Submit News about release.
31Get URL to news item 34Get URL to news item
32 35
33SF -> Admin -> File Release System 36SF -> Admin -> File Releases
34Add a release to nagiosplug and create a file release 37Add a release to nagiosplug and create a file release
35name: 1.4-alpha2. Commit 38name: 1.4-alpha2. Commit
36Step 1: Add release notes pointing to news item 39Step 1: Add release notes pointing to news item
@@ -40,5 +43,5 @@ Step 4: Send notice
40 43
41Send email to nagiosplug-help, nagios-announce 44Send email to nagiosplug-help, nagios-announce
42 45
43Change version number in configure.in and package.def 46Change to next version number in configure.in and package.def
44 47