[Nagiosplug-checkins] nagiosplug/doc LEAVERS, 1.1, 1.2 NEW_STARTERS, 1.1, 1.2 RELEASING, 1.7, 1.8

[Ton Voon]

Update of /cvsroot/nagiosplug/nagiosplug/doc
In directory sc8-pr-cvs7.sourceforge.net:/tmp/cvs-serv10089

Modified Files:
	LEAVERS NEW_STARTERS RELEASING 
Log Message:
Administrative notes


Index: LEAVERS
===================================================================
RCS file: /cvsroot/nagiosplug/nagiosplug/doc/LEAVERS,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- LEAVERS	3 May 2006 14:12:38 -0000	1.1
+++ LEAVERS	20 Jan 2007 20:06:42 -0000	1.2
@@ -9,5 +9,6 @@
   - 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
 

Index: RELEASING
===================================================================
RCS file: /cvsroot/nagiosplug/nagiosplug/doc/RELEASING,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- RELEASING	19 Sep 2005 14:18:28 -0000	1.7
+++ RELEASING	20 Jan 2007 20:06:42 -0000	1.8
@@ -5,17 +5,16 @@
 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 at cvs.sourceforge.net:/cvsroot/nagiosplug co -r r1_4-alpha2 nagiosplug
+cvs -z3 -d:ext:tonvoon at nagiosplug.cvs.sourceforge.net:/cvsroot/nagiosplug co -r r1_4_1 nagiosplug
 cd nagiosplug
 tools/setup
 ./configure
@@ -28,6 +27,7 @@
 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 @@
 
 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

Index: NEW_STARTERS
===================================================================
RCS file: /cvsroot/nagiosplug/nagiosplug/doc/NEW_STARTERS,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- NEW_STARTERS	9 Nov 2005 09:31:58 -0000	1.1
+++ NEW_STARTERS	20 Jan 2007 20:06:42 -0000	1.2
@@ -4,17 +4,21 @@
 
 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