* Makefile.am (git-tag-release): Do not check that the version number
NEWS is updated w.r.t. $(VERSION); given the new way we manage NEWS,
that would cause gratuitous spurious failures.
* HACKING: Update.
Signed-off-by: Stefano Lattarini <stefano.lattar...@gmail.com>
---
HACKING | 8 ++++----
Makefile.am | 3 ---
2 files changed, 4 insertions(+), 7 deletions(-)
diff --git a/HACKING b/HACKING
index 7ab4e7f..6966384 100644
--- a/HACKING
+++ b/HACKING
@@ -238,10 +238,10 @@
./bootstrap.sh && ./configure && make && make check && make distcheck
* Run "make git-tag-release".
- This will run the maintainer checks, check that the NEWS file is
- up-to-date, check that the local git repository and working tree
- are clean and up-to-date, and create a proper signed git tag for
- the release (based on the contents of $(VERSION)).
+ This will run the maintainer checks, verify that the local git
+ repository and working tree are clean and up-to-date, and create
+ a proper signed git tag for the release (based on the contents
+ of $(VERSION)).
* Run "make git-upload-release".
This will first verify that you are releasing from a tagged version
diff --git a/Makefile.am b/Makefile.am
index f15ede4..8bd723e 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -697,9 +697,6 @@ git-tag-release: maintainer-check
esac; \
$(determine_release_type); \
$(git_must_have_clean_workdir); \
-## Make sure the NEWS file is up-to-date.
- sed 1q $(srcdir)/NEWS | grep '$(VERSION)' >/dev/null \
- || fatal "NEWS not updated"; \
## If all was successful, tag the release in the local repository.
$$run $(GIT) tag -s "v$(VERSION)" -m "$$release_type $(VERSION)"
--
1.7.9.5
