aboutsummaryrefslogtreecommitdiff
path: root/doc/RELEASING
blob: 0f708f39a4896cb8f4b5d0602b244fed48dcff24 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
NOTES ON RELEASING NEW VERSION OF NAGIOSPLUG

cvs update in main area
. tools/devmode, if feeling adventurous
check compilation

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?

checkout new version:
cd /tmp
rm -fr nagiosplug
cvs -z3 -d:ext:tonvoon@cvs.sourceforge.net:/cvsroot/nagiosplug co -r r1_4-alpha2 nagiosplug
cd nagiosplug
tools/setup
./configure
make dist

ftp upload.sf.net
anonymous/email
bin
cd /incoming
put file

SF -> Submit News about release.
Get URL to news item

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
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