summaryrefslogtreecommitdiff
path: root/top/README-release
diff options
context:
space:
mode:
authorAkim Demaille <akim@lrde.epita.fr>2012-09-20 11:10:34 +0200
committerAkim Demaille <akim@lrde.epita.fr>2012-09-25 11:50:54 +0200
commitb9a38b4535158a96606a72d41ae3456509356935 (patch)
tree1f483e897109f7c1ae982f031b165998f3881b85 /top/README-release
parentaca9380111bb5df9f12b1aa38b6c202f97df6ac7 (diff)
downloadgnulib-b9a38b4535158a96606a72d41ae3456509356935.tar.gz
maint.mk: provide "make upload" to ease uploading
See <http://lists.gnu.org/archive/html/bug-gnulib/2012-08/msg00028.html>. Do not depend simply on the current $(VERSION), as there may have been new commits since the tarball generation. Rather, rely on $(RELEASE), as "make release-commit" already does. For consistency, add "make release RELEASE='X.Y TYPE'" as an alias for "make TYPE". * top/maint.mk (upload_command, upload, release): New. (RELEASE_TYPE): If undefined, default to the second word of $(RELEASE). (VERSION): first word of $(RELEASE) is always right. (emit_upload_commands): Adjust. * top/README-release: Update.
Diffstat (limited to 'top/README-release')
-rw-r--r--top/README-release15
1 files changed, 9 insertions, 6 deletions
diff --git a/top/README-release b/top/README-release
index 9c47528166..17f026a2c7 100644
--- a/top/README-release
+++ b/top/README-release
@@ -31,18 +31,18 @@ Here are most of the steps we (maintainers) follow when making a release.
make check syntax-check distcheck
-* To (i) set the date, version number, and release type [stable/alpha/beta]
- on line 3 of NEWS, (ii) commit that, and (iii) tag the release, run
+* To (i) set the date, version number, and release TYPE on line 3 of
+ NEWS, (ii) commit that, and (iii) tag the release, run
- make release-commit RELEASE='X.Y stable'
+ # "TYPE" must be stable, beta or alpha
+ make release-commit RELEASE='X.Y TYPE'
* Run the following to create release tarballs. Your choice selects the
corresponding upload-to destination in the emitted gnupload command.
The different destinations are specified in cfg.mk. See the definitions
of gnu_ftp_host-{alpha,beta,stable}.
- # "TYPE" must be stable, beta or alpha
- make TYPE
+ make release RELEASE='X.Y TYPE'
* Test the tarball. Copy it to a few odd-ball systems and ensure that
it builds and passes all tests.
@@ -53,7 +53,10 @@ Here are most of the steps we (maintainers) follow when making a release.
Once all the builds and tests have passed,
-* Run the gnupload command that was suggested by your "make TYPE" run above.
+* Run the gnupload command that was suggested by your "make release"
+ run above, or run
+
+ make upload RELEASE='X.Y TYPE'
* Wait a few minutes (maybe up to 30?) and then use the release URLs to
download all tarball/signature pairs and use gpg --verify to ensure