summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorStefano Lattarini <stefano.lattarini@gmail.com>2012-05-19 15:11:36 +0200
committerStefano Lattarini <stefano.lattarini@gmail.com>2012-05-19 15:12:22 +0200
commita36a8f6e7f52521d3c5d9f382ab5a4e7676b42f1 (patch)
tree640662c629fb76b2a86ecc70ff22d8217ec4c9d9 /HACKING
parent91ac5d2cf4ad0f1b28776d06a713118a4b191a47 (diff)
downloadautomake-a36a8f6e7f52521d3c5d9f382ab5a4e7676b42f1.tar.gz
release: remove overly picky check
* 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.lattarini@gmail.com>
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING8
1 files changed, 4 insertions, 4 deletions
diff --git a/HACKING b/HACKING
index 7ab4e7f25..696638447 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