e.g., APIVERSION=1.17 for the pretest 1.17.90, even though it's
leading up to 1.18.
+* grep $newversion NEWS # ensure that the NEWS file has the new version.
+
* Create an announcement message with "make announcement". Edit the
generated 'announcement' file appropriately, in particularly filling
in by hand any "TODO" left in there. In particular, thank people who
reltype=alpha # or beta or stable
host=`if test $reltype = stable; then echo ftp; else echo alpha; fi`
gpgkey=0x... # gpg --fingerprint
- $gnulib/build-aux/announce-gen --release-type=$reltype \
- --package-name=$pkg --previous-version=$prever \
- --current-version=$newver --gpg-key-id=$gpgkey \
- --news-file=NEWS \
+ $gnulib/build-aux/announce-gen \
+ --release-type=$reltype \
+ --package-name=$pkg \
+ --previous-version=$prever \
+ --current-version=$newver \
+ --gpg-key-id=$gpgkey \
+ --news=NEWS \
--url-directory=https://$host.gnu.org/gnu/$pkg
and merge this with the just-written announcement file.