Fix web manual generation details in release instructions.

* HACKING (Release Procedure): Move the instruction for generating
web manuals for a new release to before the instruction that bumps
the version numbers to the post release values.
This commit is contained in:
Gary V. Vaughan 2010-06-05 03:52:43 +07:00
parent 8524eb8f5c
commit 4a649e5c36
2 changed files with 10 additions and 2 deletions

View File

@ -1,5 +1,10 @@
2010-06-05 Gary V. Vaughan <gary@gnu.org>
Fix web manual generation details in release instructions.
* HACKING (Release Procedure): Move the instruction for generating
web manuals for a new release to before the instruction that bumps
the version numbers to the post release values.
Set SCM version number to 2.2.9a.
* configure.ac, libltdl/configure.ac (AC_INIT): Bump version
number to 2.2.9a.

View File

@ -722,6 +722,9 @@ or obtained by writing to the Free Software Foundation, Inc.,
between the previous release tarball and the new with detached gpg
signature files and clear signed directive files.
* If not an alpha, generate with `make -f[../]Makefile.maint
web-manual'.
* Upload release tarballs and diff files, plus their associated
detached gpg signature files and clear signed directive files to
ftp-upload.gnu.org. If the upload is destined for ftp.gnu.org, then the
@ -740,9 +743,9 @@ or obtained by writing to the Free Software Foundation, Inc.,
* Update the webpages, libtool.html will need to indicate the latest
release number.
* If not an alpha, upload new manual pages with cvs to:
* If not an alpha, upload new manual pages you created earlier in
doc/manual using cvs to here:
<yourusername>@cvs.savannah.gnu.org:/webcvs/libtool
(generate with `make -f[../]Makefile.maint web-manual').
* In the build directory, run `Make -f[../]Makeflie.maint announce-gen'.