diff options
| -rw-r--r-- | doc/RELEASING | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/RELEASING b/doc/RELEASING index 4f61c301..0f708f39 100644 --- a/doc/RELEASING +++ b/doc/RELEASING | |||
| @@ -11,6 +11,9 @@ commit new ChangeLog | |||
| 11 | 11 | ||
| 12 | Check configure.in with right version | 12 | Check configure.in with right version |
| 13 | cvs tag r1_4-alpha2 | 13 | cvs tag r1_4-alpha2 |
| 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? | ||
| 14 | 17 | ||
| 15 | checkout new version: | 18 | checkout new version: |
| 16 | cd /tmp | 19 | cd /tmp |
| @@ -30,7 +33,7 @@ put file | |||
| 30 | SF -> Submit News about release. | 33 | SF -> Submit News about release. |
| 31 | Get URL to news item | 34 | Get URL to news item |
| 32 | 35 | ||
| 33 | SF -> Admin -> File Release System | 36 | SF -> Admin -> File Releases |
| 34 | Add a release to nagiosplug and create a file release | 37 | Add a release to nagiosplug and create a file release |
| 35 | name: 1.4-alpha2. Commit | 38 | name: 1.4-alpha2. Commit |
| 36 | Step 1: Add release notes pointing to news item | 39 | Step 1: Add release notes pointing to news item |
| @@ -40,5 +43,5 @@ Step 4: Send notice | |||
| 40 | 43 | ||
| 41 | Send email to nagiosplug-help, nagios-announce | 44 | Send email to nagiosplug-help, nagios-announce |
| 42 | 45 | ||
| 43 | Change version number in configure.in and package.def | 46 | Change to next version number in configure.in and package.def |
| 44 | 47 | ||