+2011-12-10 Stefano Lattarini <stefano.lattarini@gmail.com>
+
+ release: don't run "make distcheck" automatically
+ * Makefile.am (git-dist): The developers should test extensively
+ before finally creating the release tarball; so don't run "make
+ distcheck" on their behalf here; instead ...
+ * HACKING (Release procedure): ... state here that "make check"
+ and "make distcheck" should be run before calling "make git-dist".
+
2011-12-09 Jim Meyering <meyering@redhat.com>
Stefano Lattarini <stefano.lattarini@gmail.com>
* Update ChangeLog.
-* Run ./bootstrap, ./configure, make.
+* Run "./bootstrap && ./configure && make && make check && make distcheck".
* Run `make release-stats' if release statistics in doc/automake.texi
have not been updated yet.
echo "NEWS not updated; not releasing" 1>&2; \
exit 1; \
fi
-## Build the distribution
- $(MAKE) $(AM_MAKEFLAGS) distcheck
+## Build the distribution. We expect the developer to have already run
+## "make check" and "make distcheck" on his own (as required in the
+## HACKING file, section "Release procedure").
+ $(MAKE) $(AM_MAKEFLAGS) dist
## Finally, if anything was successful, commit the last changes and tag
## the release in the repository. We don't use RCS keywords so it's OK
## to distribute the files before they were committed.
echo "NEWS not updated; not releasing" 1>&2; \
exit 1; \
fi
- $(MAKE) $(AM_MAKEFLAGS) distcheck
+ $(MAKE) $(AM_MAKEFLAGS) dist
cd $(srcdir) && git commit -a -s && \
git tag -s "v$(VERSION)" -m "Release $(VERSION)"