From: Stefano Lattarini Date: Thu, 30 May 2013 13:18:11 +0000 (+0200) Subject: announcement: can be generated from development snapshots as well X-Git-Tag: v1.13b~1^2~1 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=4882d43ec7ae7d9d9d9b83c388a50ec660329258;p=platform%2Fupstream%2Fautomake.git 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 --- diff --git a/maint.mk b/maint.mk index edf05bb9d..93259f1c3 100644 --- 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; \