From: Stefano Lattarini Date: Sat, 17 Nov 2012 18:42:58 +0000 (+0100) Subject: hacking: release procedure: fix order of some steps X-Git-Tag: v1.12.6~29 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=d85a97bd08ddbb224124ae3a6cc27930b8db55ec;p=platform%2Fupstream%2Fautomake.git hacking: release procedure: fix order of some steps * HACKING (Release procedure): The manuals should be rebuilt and uploaded at at www.gnu.org *before* bumping the version number to the next alpha release. Signed-off-by: Stefano Lattarini --- diff --git a/HACKING b/HACKING index e245039..d69c75d 100644 --- a/HACKING +++ b/HACKING @@ -258,12 +258,6 @@ locations. In case you need to sign with a non-default key, you can use "make GNUPLOADFLAGS='--user KEY' git-upload-release". -* Update version number in configure.ac to next alpha number. - Re-run ./bootstrap.sh and commit. - -* Don't forget to "git push" your changes so they appear in the public - git tree. - * For stable releases, update the manuals at www.gnu.org: - Generate manuals: cd doc @@ -275,6 +269,12 @@ - Check for link errors, fix them, recheck until convergence: +* Update version number in configure.ac to next alpha number. + Re-run ./bootstrap.sh and commit. + +* Don't forget to "git push" your changes so they appear in the public + git tree. + * Send the announcement at least to and . If the release is a stable one, the announcement must also go to ; if it is an alpha or beta release,