summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 0074c80)
raw | patch | inline | side by side (parent: 0074c80)
author | Ton Voon <tonvoon@users.sourceforge.net> | |
Fri, 4 Mar 2005 21:03:43 +0000 (21:03 +0000) | ||
committer | Ton Voon <tonvoon@users.sourceforge.net> | |
Fri, 4 Mar 2005 21:03:43 +0000 (21:03 +0000) |
git-svn-id: https://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/trunk@1143 f882894a-f735-0410-b71e-b25c423dba1c
doc/RELEASING | patch | blob | history |
diff --git a/doc/RELEASING b/doc/RELEASING
index 4f61c3018e3dd85c1155443e71fb6a0a1f0971aa..0f708f39a4896cb8f4b5d0602b244fed48dcff24 100644 (file)
--- a/doc/RELEASING
+++ b/doc/RELEASING
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
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
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