From 0c9c7770b7fd6c7d7bec1b1592e568fafa7d0005 Mon Sep 17 00:00:00 2001 From: Jonas Fonseca Date: Tue, 4 Mar 2008 11:12:35 +0100 Subject: [PATCH] Add rebuilding manpages as a release task --- doc/release.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/release.txt b/doc/release.txt index 28e1882b..8eb76f5a 100644 --- a/doc/release.txt +++ b/doc/release.txt @@ -13,7 +13,9 @@ When releasing a new version Don't add the release date yet though; it will be added after the release, from the date in the mailing list archives. - Change VERSION in the top of configure.in to hold the new version number. - - Commit only this change. + - Update the manpages so the will have the new release number by first + building the source, followed by making the `update-man' target in doc/. + - Commit these changes. - Create a signed tag having the version ("ELinks X.X.X") as the subject and using the changelog create above as the body. Use something like: