summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--doc/LEAVERS14
-rw-r--r--doc/NEW_STARTERS24
-rw-r--r--doc/RELEASING47
3 files changed, 0 insertions, 85 deletions
diff --git a/doc/LEAVERS b/doc/LEAVERS
deleted file mode 100644
index 9764fda..0000000
--- a/doc/LEAVERS
+++ /dev/null
@@ -1,14 +0,0 @@
1LEAVERS
2
3These are the steps for someone leaving the team.
4
5Leaver has to:
6 - Update all current tracker items
7
8Administration tasks:
9 - Reassign leaver's tracker items to project lead
10 - Remove from Sourceforge's list of developers. This will include CVS access. Do not
11 need to remove from CVS avail file
12 - If applicable, remove from mailing list administrators
13 - Keep on nagiosplug-team mailing list, unless specifically requested to be removed
14
diff --git a/doc/NEW_STARTERS b/doc/NEW_STARTERS
deleted file mode 100644
index 23f1a4a..0000000
--- a/doc/NEW_STARTERS
+++ /dev/null
@@ -1,24 +0,0 @@
1NEW STARTERS
2
3These are the steps for adding someone to the team.
4
5Need to know:
6 - Name
7 - Primary email for nagiosplug-team mailings
8 - Sourceforge id
9 - Type of member (translator, developer, release manager, project administrator)
10
111. Add member to nagiosplug-team mailing list (https://lists.sourceforge.net/lists/admin/nagiosplug-team)
12 and to the nagiosplug-checkins mailing list (https://lists.sourceforge.net/lists/admin/nagiosplug-checkins,
13 add sourceforge email address via Privacy Options->Sender filters)
142. Add Sourceforge access:
15 - Translator: CVS access, Shell access, Release Tech (no)
16 - Developer: Project role: Developer, CVS access, Shell access, Release Tech (no), Task Manager (A&T),
17 Forums (Moderator), Doc Manager (Editor)
18 Update Developer Permissions.
19 For each tracker, set to Technician (need to add all trackers first, then change to
20 technician for each one)
213. Add to CVS avail file:
22 - Translator: Add member to translation files
23 - Developer: Add member to CVSROOT/avail for all files
244. Send email to nagiosplug-team introducing new member
diff --git a/doc/RELEASING b/doc/RELEASING
deleted file mode 100644
index c5d8195..0000000
--- a/doc/RELEASING
+++ /dev/null
@@ -1,47 +0,0 @@
1NOTES ON RELEASING NEW VERSION OF NAGIOSPLUG
2
3svn update in main area
4. tools/devmode, if feeling adventurous
5check compilation, check tinderbox screens
6
7Update BUGS, NEWS file
8Update AUTHORS if new members
9Update configure.in and package.def with version
10Run svn2cl (get from http://ch.tudelft.nl/~arthur/svn2cl):
11svn2cl.sh --break-before-msg --reparagraph -i http://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/trunk
12commit BUGS NEWS configure.in package.def ChangeLog
13
14svn copy http://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/trunk
15http://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/tags/release-1.4.10
16
17checkout new version:
18cd /tmp
19rm -fr nagiosplug
20svn export http://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/tags/release-1.4.10 nagiosplug
21cd nagiosplug
22tools/setup
23./configure
24make dist
25
26sftp upload.sf.net
27cd uploads
28put file
29
30SF -> Submit News about release. Make sure it is called "Nagios Plugins" (with those caps)
31Link to download at http://sourceforge.net/project/showfiles.php?group_id=29880
32Include contents of NEWS for this release
33List all people on team involved.
34Add acknowledgement to contributors
35Submit. Get URL to news item
36
37SF -> Admin -> File Releases
38Add a release to nagiosplug and create a file release
39Name: 1.4.1
40Create release
41Step 1: Add release notes pointing to news item
42Step 2: add file
43Step 3: *.tar.gz, Platform Independent, Source .gz
44Step 4: Send notice
45
46Send email to nagiosplug-help, nagios-announce with the news text
47Add a news item to http://nagiosplugins.org