From 20fe3a947f2305fb271a811d50f8a7d263511ee7 Mon Sep 17 00:00:00 2001 From: Dan Harkless Date: Tue, 9 May 2000 08:16:18 +0000 Subject: [PATCH] Added steps to README.developers saying to change the version number to X.Y.Z+dev. Did a little rearranging and changed the FTP dir from /home/ftp to /var/ftp to reflect Doug's new machine. --- ChangeLog | 10 +++++++--- docs/README.developers | 21 +++++++++++++++------ 2 files changed, 22 insertions(+), 9 deletions(-) diff --git a/ChangeLog b/ChangeLog index 3bb7d27..d26f289 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,13 +1,17 @@ -Tue May 09 00:50:39 2000 Dan Harkless +Tue May 09 01:13:52 2000 Dan Harkless * Alphabetized Shantonu's $pop_kinds output on configure's "pop is enabled" line. If POP3 is the only kind of POP enabled, say so, rather than just saying "yes" (which is ambiguous). - * Got rid of four warnings in Shantonu's new getpass.c. Needed to + * Fixed four warnings in Shantonu's new getpass.c. Needed to #include for calloc(), for ttyname(), and "h/mh.h" for adios(). Also changed ch from char to int to get rid - of "comparison is always 1 due to limited range of data type" on EOF. + of "comparison is always 1 due to limited range of data type" on EOF. + + * Added steps to README.developers saying to change the version + number to X.Y.Z+dev. Did a little rearranging and changed the FTP + dir from /home/ftp to /var/ftp to reflect Doug's new machine. Mon May 08 23:51:55 2000 Dan Harkless diff --git a/docs/README.developers b/docs/README.developers index ec2d243..b2c2efa 100644 --- a/docs/README.developers +++ b/docs/README.developers @@ -150,7 +150,7 @@ account, danh, as examples here): 6. Untar nmh-1.0.4.tar.gz and `diff -r' it vs. your CVS tree. Make sure no files got left out of the distribution that should be in it (due to someone - forgetting to update the DIST variables in the makefiles). + forgetting to update the DIST variables in the Makefiles). 7. If you have root access on your machine, it's good at this point to do: @@ -163,14 +163,23 @@ account, danh, as examples here): making it possible for that user to Trojan the nmh code before the system administrator finishes installing it. - 8. Preferably make an MD5 hash and/or a PGP signature of nmh-1.0.4.tar.gz. + 8. Make sure your new tarball uncompresses and untars with no problem. Make + sure you can configure, make, and install nmh from it. - 9. Preferably test out the tarball, making sure you can uncompress and untar - it, and configure, make, install, and use nmh from it. + 9. If all is well and your tarball is final, go back to your CVS tree and do: -10. % scp -p nmh-1.0.4.tar.gz* danh@mhost.com:/home/ftp/pub/nmh + % echo 1.0.4+dev > VERSION -11. Send an announcement to exmh-users@redhat.com, exmh-workers@redhat.com, +10. Put a comment like "Upped the version number to 1.0.4+dev until the next nmh + release." in the ChangeLog. + +11. % cvs commit ChangeLog VERSION + +12. If possible, make an MD5 hash and/or a PGP signature of nmh-1.0.4.tar.gz. + +13. % scp -p nmh-1.0.4.tar.gz* danh@mhost.com:/var/ftp/pub/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 -- 1.7.10.4