Rename configure.in to configure.ac

[~andy/gtk] / docs / RELEASE-HOWTO

diff --git a/docs/RELEASE-HOWTO b/docs/RELEASE-HOWTO
index 4991d9a9f1ea18c32410e868ebb876322e525e6e..8aeb7b3ebdadfa0f8422de429d5ad57af19c6a03 100644 (file)
--- a/docs/RELEASE-HOWTO
+++ b/docs/RELEASE-HOWTO
@@ -7,6 +7,7 @@ dependencies:
 * gtk-doc
 * docbook-utils
 Without those packages make distcheck will *not* pass.
+Make sure that gtk-doc is the latest released version.
 
 
  0) Go back to a pristine working directory. With git, this works:
@@ -28,9 +29,9 @@ Without those packages make distcheck will *not* pass.
  3) In particular, if this is a major, stable, release, verify that
     README.in contains the relevant release notes and that the
     required versions of dependencies in INSTALL.in are in sync
-    with configure.in.
+    with configure.ac.
 
- 4) Verify that the version in configure.in has been bumped after the last
+ 4) Verify that the version in configure.ac has been bumped after the last
     release. (Note that this is critical, a slip-up here will cause the
     soname to change).
 
@@ -77,7 +78,7 @@ Without those packages make distcheck will *not* pass.
 
     git push origin refs/tags/2.12.10
 
-13) Bump the version number in configure.in and commit and push this change
+13) Bump the version number in configure.ac and commit and push this change
 
 14) Upload the tarball to master.gnome.org and run install-module to transfer
     it to download.gnome.org. If you don't have an account on master.gnome.org,
@@ -101,7 +102,7 @@ Without those packages make distcheck will *not* pass.
     summary of changes.
 
 18) Send it to gnome-announce-list, gtk-list, gtk-app-devel-list and
-    gtk-devel-list. Set reply-to to gnome-hackers.
+    gtk-devel-list. Set reply-to to desktop-devel-list.
 
 19) Add a link to the release announcement to www.gtk.org which lives
-    in the gtk-web cvs module.
+    in the gtk-web git module.