X-Git-Url: https://arthur.barton.de/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2FHowToRelease.txt;h=a5270981aec66c865e4326e02afb33a363ddaa4b;hb=6a622c0084ec69563609804520e2753501254503;hp=d4d82bc79e2dcb979fe2fa03ff47940f30449a65;hpb=01c39ba0015f715b2082f5ed54dc769d09c09bd0;p=ngircd-alex.git

diff --git a/doc/HowToRelease.txt b/doc/HowToRelease.txt
index d4d82bc7..a5270981 100644
--- a/doc/HowToRelease.txt
+++ b/doc/HowToRelease.txt
@@ -1,9 +1,8 @@
 
                      ngIRCd - Next Generation IRC Server
+                           http://ngircd.barton.de/
 
-                        (c)2001-2010 Alexander Barton,
-                    alex@barton.de, http://www.barton.de/
-
+               (c)2001-2018 Alexander Barton and Contributors.
                ngIRCd is free software and published under the
                    terms of the GNU General Public License.
 
@@ -37,10 +36,11 @@ II. How to prepare a new ngIRCd release?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 a) Make sure the source tree is in a releasable state ;-)
+    - is the AUTHORS file up to date?
 
 b) Make sure you have working versions of GNU autoconf and GNU automake
    installed on the system you use for generating the release:
-   as of October 2010 we are using GNU autoconf 2.61 and GNU automake 1.10.1
+   as of October 2010 we are using GNU autoconf 2.67 and GNU automake 1.11.1
    which seem to work just fine.
 
 c) Update the files describing the new release:
@@ -72,6 +72,6 @@ k) Sign the distribution archive(s) using GnuPG: "gpg -b <archivefile>"
 l) Upload and distribute the newly generated ngIRCd release archive(s)
    and GnuPG signatures.
 
-m) Write an announcement to the mailing list, freshmeat, Twitter, ...
+m) Write an announcement to the mailing list, Twitter, ...
 
 n) Relax :-)