X-Git-Url: http://git.marmaro.de/?a=blobdiff_plain;f=docs%2FREADME.developers;h=abfb3e568b8603c5e3369653948442a5e54c0d38;hb=c6abf17d7aceffcce6ff2a871cc4d95bc31fc5bf;hp=20b64527e2e85678b6d832fe90848a7378067b47;hpb=557d33aeabe46e9a0411959703f721c5b9ce2ae9;p=mmh

diff --git a/docs/README.developers b/docs/README.developers
index 20b6452..abfb3e5 100644
--- a/docs/README.developers
+++ b/docs/README.developers
@@ -1,8 +1,6 @@
 #
 # README.developers
 #
-# $Id$
-#
 
 This file is intended to provide a few tips for anyone doing development on nmh.
 Developers who learn things "the hard way" about the nmh codebase (as opposed to
@@ -28,12 +26,10 @@ view of the developers (and the autoconf script).
 
 Note that the automatically generated autoconf files (such as config.h.in,
 stamp-h.in, and configure), are NOT kept in CVS.  Thus, when you check out
-a CVS tree, you need to do the following things before you can build
+a CVS tree, you need to run the autogen.sh script before you can build
 anything:
 
-	% autoheader
-	% autoconf
-	% date > stamp-h.in
+	% ./autogen.sh
 
 -------------------
 directory structure
@@ -143,7 +139,8 @@ releasing nmh
 -------------
 
 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,21 +183,46 @@ account, danh, as examples here):
 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
+
+    You can verify the signature with
+    % gpg --verify nmh-1.0.4.tar.gz.sig nmh-1.0.4.tar.gz
+
+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* youruser@dl.sv.nongnu.org:/releases/nmh/
 
-13. % scp -p nmh-1.0.4.tar.gz* danh@mhost.com:/var/ftp/pub/nmh
+14. Update the http://www.nongnu.org/nmh/ homepage. (It lives in the 'webpages
+    repository'; see https://savannah.nongnu.org/cvs/?group=nmh)
 
-14. Send an announcement to exmh-users@redhat.com, exmh-workers@redhat.com,
-    mh-users@ics.uci.edu, and nmh-announce@mhost.com.  If the release fixes
-    significant security holes, also send an announcement to
-    bugtraq@securityfocus.com.  The exmh lists require you to be subscribed in
-    order to post.  Note that you don't need to post separately to comp.mail.mh,
-    as the mh-users mailing list is apparently bidirectionally gatewayed to it.
+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).
+
+16. Send the release announcement email to the following places:
+     nmh-workers@nongnu.org
+     nmh-announce@nongnu.org
+     exmh-users@redhat.com
+     exmh-workers@redhat.com
+     mh-e-users@lists.sourceforge.net
+     mh-users@ics.uci.edu *or* comp.mail.mh (there is a bidirectional gateway)
+
+    If the release fixes significant security holes, also send an announcement
+    to bugtraq@securityfocus.com.  The exmh lists require you to be subscribed
+    in order to post.  Note that you don't need to post separately to
+    comp.mail.mh, as the mh-users mailing list is apparently bidirectionally
+    gatewayed to it.
 
     Preferably, the announcement should contain the MD5 hash generated above,
-    and should be PGP-signed.  It should include the FTP URL for the tarball as
+    and should be PGP-signed.  It should include the URL for the tarball as
     well as the URL of the website.  It should contain a brief summary of
     visible changes, as well as the URL of the cvsweb diff page that would show
-    a detailed list of changes.  The changes between 1.0.3 and 1.0.4 would be
+    a detailed list of changes.  The changes between 1.2 and 1.3 would be
     shown by:
 
-        http://www.mhost.com/cgi-bin/cvsweb/nmh/ChangeLog?r1=1.40&r2=1.71
+        http://cvs.savannah.gnu.org/viewvc/nmh/ChangeLog?root=nmh&r1=1.215&r2=1.254.2.13
+