X-Git-Url: https://arthur.barton.de/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2FHowToRelease.txt;h=10343cd4f607fbc0d1894e92aed01c2c341b7bfd;hb=2ff76d7f480b87e811af81cf9eaa9822b77863c4;hp=1905e184bf9f401a145ac175588a23559fdd472f;hpb=96bad2b861cffcd7724cf26464da4568852241de;p=ngircd-alex.git diff --git a/doc/HowToRelease.txt b/doc/HowToRelease.txt index 1905e184..10343cd4 100644 --- a/doc/HowToRelease.txt +++ b/doc/HowToRelease.txt @@ -2,7 +2,7 @@ ngIRCd - Next Generation IRC Server http://ngircd.barton.de/ - (c)2001-2019 Alexander Barton and Contributors. + (c)2001-2021 Alexander Barton and Contributors. ngIRCd is free software and published under the terms of the GNU General Public License. @@ -35,19 +35,27 @@ up-to-date (e.g. using ./autogen.sh) before generating the archives! 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 +a) 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.67 and GNU automake 1.11.1 + as of May 2020 we are using GNU autoconf 2.69 and GNU automake 1.11.6 which seem to work just fine. + NOTE: new releases of GNU automake DO NOT work, as they lack support for + the "ansi2knr" wrapper and "de-ANSI-fication" support! + +b) Make sure the source tree is in a releasable state ;-) + - Are all branches & patches merged? Check GitHub issues, pull requests + and milestones! + - Run as many tests as you can! + - Is the AUTHORS file up to date? This command may be helpful: + "( grep '>$' AUTHORS; git shortlog -se | cut -c8- ) | grep -Ev \ + '(alex@barton.de|fw@strlen.de)' | LC_ALL=de_DE.UTF-8 sort -u" c) Update the files describing the new release: - ChangeLog - NEWS d) Update the version numbers in the following files: + - contrib/de.barton.ngircd.metainfo.xml - contrib/ngircd.spec e) Generate a new Debian change log entry in the following file, e.g. using