[Nmh-commits] nmh docs/README.developers ChangeLog

[Peter Maydell]

CVSROOT:        /cvsroot/nmh
Module name:    nmh
Changes by:     Peter Maydell <pm215>   08/04/27 20:58:50

Modified files:
        docs           : README.developers 
        .              : ChangeLog 

Log message:
        Update some of the 'how to do a release' documentation

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/nmh/docs/README.developers?cvsroot=nmh&r1=1.21&r2=1.22
http://cvs.savannah.gnu.org/viewcvs/nmh/ChangeLog?cvsroot=nmh&r1=1.256&r2=1.257

Patches:
Index: docs/README.developers
===================================================================
RCS file: /cvsroot/nmh/nmh/docs/README.developers,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- docs/README.developers      5 Sep 2003 21:07:49 -0000       1.21
+++ docs/README.developers      27 Apr 2008 20:58:50 -0000      1.22
@@ -1,7 +1,7 @@
 #
 # README.developers
 #
-# $Id: README.developers,v 1.21 2003/09/05 21:07:49 kenh Exp $
+# $Id: README.developers,v 1.22 2008/04/27 20:58:50 pm215 Exp $
 #
 
 This file is intended to provide a few tips for anyone doing development on 
nmh.
@@ -143,7 +143,8 @@
 -------------
 
 To make a public release of nmh (we'll use version 1.0.4 and my mhost.com
-account, danh, as examples here):
+account, danh, as examples here; the convention for release candidates
+is to use something like "1.0.4-RC1"):
 
  1. % echo 1.0.4 > VERSION
     % date +"%e %B %Y" > DATE
@@ -186,10 +187,24 @@
 11. % cvs commit ChangeLog VERSION
 
 12. If possible, make an MD5 hash and/or a PGP signature of nmh-1.0.4.tar.gz.
+    Assuming you have gpg set up, this should be:
+    % gpg --output nmh-1.0.4.tar.gz.sig --detach-sig nmh-1.0.4.tar.gz
 
-13. % scp -p nmh-1.0.4.tar.gz* address@hidden:/var/ftp/pub/nmh
+    You can verify the signature with
+    % gpg --verify nmh-1.0.4.tar.gz.sig nmh-1.0.4.tar.gz
 
-14. Send an announcement to address@hidden, address@hidden,
+13. Upload the files to savannah. First make sure they are mode 664 so
+    they will have the right permissions on the server end
+    (see https://savannah.gnu.org/maintenance/SharedDownloadArea)
+    % chmod 664 nmh-1.0.4.tar.gz*
+
+    Then scp them across:
+    % scp -p nmh-1.0.4.tar.gz* address@hidden:/releases/nmh/
+
+14. FIXME -- I suspect that at least some of the mailing lists here are not
+    correct any more. Needs checking.
+
+    Send an announcement to address@hidden, address@hidden,
     address@hidden, and address@hidden  If the release fixes
     significant security holes, also send an announcement to
     address@hidden  The exmh lists require you to be subscribed in
@@ -204,3 +219,6 @@
     shown by:
 
         http://www.mhost.com/cgi-bin/cvsweb/nmh/ChangeLog?r1=1.40&r2=1.71
+
+15. Add a news item to the savannah nmh page. You'll have to submit it first
+    and then separately approve it (under News->Manage).

Index: ChangeLog
===================================================================
RCS file: /cvsroot/nmh/nmh/ChangeLog,v
retrieving revision 1.256
retrieving revision 1.257
diff -u -b -r1.256 -r1.257
--- ChangeLog   27 Apr 2008 20:55:28 -0000      1.256
+++ ChangeLog   27 Apr 2008 20:58:50 -0000      1.257
@@ -1,5 +1,7 @@
 2008-04-27  Peter Maydell  <address@hidden>
 
+       * Updated some of the 'how to do a release' documentation.
+
        * Upped the VERSION string to '1.3-dev', since 1.3-RC1 has
        been branched off.