summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 291a30d)
raw | patch | inline | side by side (parent: 291a30d)
author | Ton Voon <tonvoon@users.sourceforge.net> | |
Mon, 19 Sep 2005 13:46:04 +0000 (13:46 +0000) | ||
committer | Ton Voon <tonvoon@users.sourceforge.net> | |
Mon, 19 Sep 2005 13:46:04 +0000 (13:46 +0000) |
git-svn-id: https://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/trunk@1226 f882894a-f735-0410-b71e-b25c423dba1c
doc/RELEASING | patch | blob | history |
diff --git a/doc/RELEASING b/doc/RELEASING
index 0f708f39a4896cb8f4b5d0602b244fed48dcff24..c1c9d06eaf7543b35c1acc8b07fa126ff941102f 100644 (file)
--- a/doc/RELEASING
+++ b/doc/RELEASING
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
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