Administrative notes

git-svn-id: https://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/trunk@1572 f882894a-f735-0410-b71e-b25c423dba1c

diff --git a/doc/LEAVERS b/doc/LEAVERS
index 0040a191dda3d63567766fbdbda979a6708eff00..9764fda8c1eac613740228f241b1170cb94e68ed 100644 (file)
--- a/doc/LEAVERS
+++ b/doc/LEAVERS
@@ -9,5 +9,6 @@ Administration tasks:
   - Reassign leaver's tracker items to project lead
   - Remove from Sourceforge's list of developers. This will include CVS access. Do not
     need to remove from CVS avail file
+  - If applicable, remove from mailing list administrators
   - Keep on nagiosplug-team mailing list, unless specifically requested to be removed
 

diff --git a/doc/NEW_STARTERS b/doc/NEW_STARTERS
index 89a1a9a623c6fb69cc8dc6f38a07d4a2e801719e..23f1a4aa937ffe688e95aa25e9967e522aa0d8fc 100644 (file)
--- a/doc/NEW_STARTERS
+++ b/doc/NEW_STARTERS
@@ -4,17 +4,21 @@ These are the steps for adding someone to the team.
 
 Need to know:
   - Name
+  - Primary email for nagiosplug-team mailings
   - Sourceforge id
   - Type of member (translator, developer, release manager, project administrator)
 
-1. Add member to nagiosplug-team mailing list and to the nagiosplug-checkins
-   mailing list (via Privacy Options)
+1. Add member to nagiosplug-team mailing list (https://lists.sourceforge.net/lists/admin/nagiosplug-team)
+   and to the nagiosplug-checkins mailing list (https://lists.sourceforge.net/lists/admin/nagiosplug-checkins,
+   add sourceforge email address via Privacy Options->Sender filters)
 2. Add Sourceforge access:
   - Translator: CVS access, Shell access, Release Tech (no)
-  - Developer: CVS access, Shell access, Release Tech (no), Task Manager (A&T),
-               Forums (Moderator), Doc Manager (Editor). Need to set tracker
-               access individually
+  - Developer: Project role: Developer, CVS access, Shell access, Release Tech (no), Task Manager (A&T),
+               Forums (Moderator), Doc Manager (Editor)
+               Update Developer Permissions.
+              For each tracker, set to Technician (need to add all trackers first, then change to 
+               technician for each one)
 3. Add to CVS avail file:
   - Translator: Add member to translation files
   - Developer: Add member to CVSROOT/avail for all files
-
+4. Send email to nagiosplug-team introducing new member

diff --git a/doc/RELEASING b/doc/RELEASING
index 92dbb72eb99b1cb8c4d974711ccbe28143b8f2a1..d9039fffa465d85c111176e89de2987cec69cb6e 100644 (file)
--- a/doc/RELEASING
+++ b/doc/RELEASING
@@ -5,17 +5,16 @@ cvs update in main area
 check compilation
 
 Update BUGS file
-Update configure.in and package.def with version and commit
-
+Update configure.in and package.def with version
 Run cvs2cl.pl
-commit new ChangeLog
+commit BUGS configure.in package.def ChangeLog
 
 cvs tag r1_4_1
 
 checkout new version:
 cd /tmp
 rm -fr nagiosplug
-cvs -z3 -d:ext:tonvoon@cvs.sourceforge.net:/cvsroot/nagiosplug co -r r1_4-alpha2 nagiosplug
+cvs -z3 -d:ext:tonvoon@nagiosplug.cvs.sourceforge.net:/cvsroot/nagiosplug co -r r1_4_1 nagiosplug
 cd nagiosplug
 tools/setup
 ./configure
@@ -28,6 +27,7 @@ cd /incoming
 put file
 
 SF -> Submit News about release. Make sure it is called "Nagios Plugins" (with those caps)
+Link to download at http://sourceforge.net/project/showfiles.php?group_id=29880
 List major changes. 
 List all people on team involved. 
 Add acknowledgement to contributors
@@ -35,7 +35,7 @@ Get URL to news item
 
 SF -> Admin -> File Releases
 Add a release to nagiosplug and create a file release
-Name: 1.4-alpha2. Create release
+Name: 1.4.1 Create release
 Step 1: Add release notes pointing to news item
 Step 2: add file
 Step 3: *.tar.gz, Platform Independent, Source .gz