diff options
-rw-r--r-- | doc/RELEASING | 16 |
1 files changed, 7 insertions, 9 deletions
diff --git a/doc/RELEASING b/doc/RELEASING index 0f708f3..c1c9d06 100644 --- a/doc/RELEASING +++ b/doc/RELEASING | |||
@@ -9,11 +9,8 @@ Update BUGS file, if this is a major release | |||
9 | Run cvs2cl.pl | 9 | Run cvs2cl.pl |
10 | commit new ChangeLog | 10 | commit new ChangeLog |
11 | 11 | ||
12 | Check configure.in with right version | 12 | Check configure.in and package.def with right version |
13 | cvs tag r1_4-alpha2 | 13 | cvs tag r1_4_1 |
14 | If a main release (eg, non alpha/beta), branch here: | ||
15 | cvs tab -b r1_4-patches | ||
16 | Consider the SF snapshot branches - should you remove any other branches? | ||
17 | 14 | ||
18 | checkout new version: | 15 | checkout new version: |
19 | cd /tmp | 16 | cd /tmp |
@@ -31,17 +28,18 @@ cd /incoming | |||
31 | put file | 28 | put file |
32 | 29 | ||
33 | SF -> Submit News about release. | 30 | SF -> Submit News about release. |
31 | List major changes. | ||
32 | List all people on team involved. | ||
33 | Add acknowledgement to contributors | ||
34 | Get URL to news item | 34 | Get URL to news item |
35 | 35 | ||
36 | SF -> Admin -> File Releases | 36 | SF -> Admin -> File Releases |
37 | Add a release to nagiosplug and create a file release | 37 | Add a release to nagiosplug and create a file release |
38 | name: 1.4-alpha2. Commit | 38 | Name: 1.4-alpha2. Create release |
39 | Step 1: Add release notes pointing to news item | 39 | Step 1: Add release notes pointing to news item |
40 | Step 2: add file | 40 | Step 2: add file |
41 | Step 3: *.tar.gz, Platform Independent, Source .gz | 41 | Step 3: *.tar.gz, Platform Independent, Source .gz |
42 | Step 4: Send notice | 42 | Step 4: Send notice |
43 | 43 | ||
44 | Send email to nagiosplug-help, nagios-announce | 44 | Send email to nagiosplug-help, nagios-announce with the news text |
45 | |||
46 | Change to next version number in configure.in and package.def | ||
47 | 45 | ||