announcement: can be generated from development snapshots as well

And not only from checkouts corresponding exactly from a beta
or stable release.  That was only getting in the way of proper
testing for the 'announcement' recipe.

* maint.mk (determine_release_type): If the make variable
DEVEL_SNAPSHOT is set, do not error out if the current version
denotes a development snapshot (e.g., "1.13.2c" or "1.99a").
(announcement): Relax, by also accepting to run from development
snapshots, not only stable or beta releases.  Do so by defining
the target-specific variable DEVEL_SNAPSHOT to "yes".
(print-release-type): Micro enhancement while at it.

Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>

diff --git a/maint.mk b/maint.mk
index edf05bb..93259f1 100644 (file)
--- a/maint.mk
+++ b/maint.mk
@@ -153,7 +153,7 @@ determine_release_type = \
 print-release-type:
        @$(determine_release_type); \
         echo "$$release_type $(VERSION);" \
-             "it will be announced as a $$announcement_type"
+             "it will be announced as a \"$$announcement_type\""
 
 git-tag-release: maintainer-check
        @set -e -u; \