diff options
| author | Eric Blake <ebb9@byu.net> | 2009-11-21 06:17:49 -0700 |
|---|---|---|
| committer | Eric Blake <ebb9@byu.net> | 2009-11-21 06:52:48 -0700 |
| commit | 1d1145256aa2a7b9478ab0a43aac4d10bfbf7c6b (patch) | |
| tree | ba7f151f9ab1f8a20218669369e24ded0801cbd8 /HACKING | |
| parent | f6ae9102206d44004eea7332fce0f6c280e94b07 (diff) | |
| download | autoconf-1d1145256aa2a7b9478ab0a43aac4d10bfbf7c6b.tar.gz | |
Prepare for release.
* build-aux/announce-gen: Sync from upstream.
* build-aux/config.guess: Likewise.
* build-aux/config.sub: Likewise.
* cfg.mk (gnu_rel_host, url_dir_list): Move...
* maint.mk: ...here, copying ideas from gnulib.
(major): Rename...
(stable): ...to this, copying gnulib.
* HACKING (release): Document changes in process.
Signed-off-by: Eric Blake <ebb9@byu.net>
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 15 |
1 files changed, 8 insertions, 7 deletions
@@ -108,10 +108,11 @@ should check the results before committing them in git. ** Set the version number Update the version number in NEWS (with version, date, and release type) and ChangeLog, and mention in README whether the release is -stable. `make news-date-check' and `make changelog-check' will -validate that the information is formatted correctly. Make sure all -changes are committed, then run `git tag -s -m <version> -u <gpg_key> -v<version>'. Do not push anything upstream at this point. +stable. Make sure all changes are committed, then run `git tag -s -m +<version> -u <gpg_key> v<version>'. Do not push anything upstream at +this point. At this point, running `make _version', followed by `make +news-date-check changelog-check' will validate that the information is +formatted correctly. ** Update configure As much as possible, make sure to release an Autoconf that uses @@ -127,7 +128,7 @@ can run `make dist-xz'; run this prior to the release target so that the release announcement will include the .tar.xz file. ** Make the release -Run `make {alpha,beta,major}' depending on which type of release this +Run `make {alpha,beta,stable}' depending on which type of release this is. This runs the various checks, creates delta files, creates a preliminary announcement in /tmp/announce-autoconf-<version>, prints out the command to upload the files, and updates the previous version @@ -147,11 +148,11 @@ Run `git push origin refs/tags/v<version>' to push the release tag. ** Announce Complete/fix the announcement file, and email it at least to -autoconf@gnu.org and autotools-announce@gnu.org. If this is a major +autoconf@gnu.org and autotools-announce@gnu.org. If this is a stable release, also mail to info-gnu@gnu.org. ** Other web updates -For alpha and beta releases, the process is complete. For major +For alpha and beta releases, the process is complete. For stable releases, there are several other web pages that need updates. Update the online manual: Run `make web-manual', then copy the |