* HACKING: Don't describe the obsolete 'git-release' target anymore. Instead, document the new and improved targets 'git-tag-release' and 'git-upload-release' (introduced in commit v1.11-674-gaf5f939 of 25-01-2012, "release: revamp rules to tag and upload the releases"). --- HACKING | 19 +++++++++++++------ 1 files changed, 13 insertions(+), 6 deletions(-)
diff --git a/HACKING b/HACKING index 6b8760e..84440a3 100644 --- a/HACKING +++ b/HACKING @@ -200,12 +200,19 @@ * Run this: ./bootstrap && ./configure && make && make check && make distcheck -* Run "make git-release". - This will run "make dist" to create the tarballs, commit the last - changes to NEWS, configure.ac and m4/amversion.m4, tag the repository, - sign the tarballs, and upload them. - Use "make GNUPLOADFLAGS='--user key' git-release" to sign with - a non-default key. +* Run "make git-tag-release". + This will run the maintainer checks, check that the NEWS file is + up-to-date, check that the local git repository and working tree + are clean and up-to-date, and create a proper signed git tag for + the release (based on the contents of $(VERSION)). + +* Run "make git-upload-release". + This will first verify that you are releasing from a tagged version + and that the local git repository and working tree are clean and + up-to-date, and will then run "make dist" to create the tarballs, + and invoke the 'gnupload' script sign and upload them to the correct + 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 and commit. -- 1.7.9