summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorStefano Lattarini <stefano.lattarini@gmail.com>2011-12-08 21:48:25 +0100
committerStefano Lattarini <stefano.lattarini@gmail.com>2011-12-22 14:07:10 +0100
commitea67a2ea498e07aa8b2db796aa96c7f7594b98f0 (patch)
tree84a0ce342dd68fdccd6ca1bddd22e126ebf45727 /HACKING
parentf60ca932334699a765d2b51432f9533dcc9e0807 (diff)
downloadautomake-ea67a2ea498e07aa8b2db796aa96c7f7594b98f0.tar.gz
configure: print proper message for test releases
* configure.ac: If the current release is detected to be a test release or a development snapshot, print a proper warning for the user. * README-alpha: Delete, it's obsolete now (and in fact this file hasn't been touched in eleven years, since release 1.4b or so). * HACKING (Release procedure): Don't say to update README-alpha.
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING2
1 files changed, 1 insertions, 1 deletions
diff --git a/HACKING b/HACKING
index 8c437ed78..7043eb1b6 100644
--- a/HACKING
+++ b/HACKING
@@ -194,7 +194,7 @@
Commit. Unfortunately you need an FSF account to do this.
(You can also use `make fetch', but that is still woefully incomplete.)
-* Update NEWS. For an alpha release, update README-alpha.
+* Update NEWS.
* Update the version number in configure.ac.
(The idea is that every other alpha number will be a net release.