diff options
| author | Reuben Thomas <rrt@sc3d.org> | 2012-02-09 13:05:57 +0000 |
|---|---|---|
| committer | Jim Meyering <meyering@redhat.com> | 2012-02-11 10:42:43 +0100 |
| commit | e45d5577595787311accf5b60edf23ad58476f23 (patch) | |
| tree | cc1a665422784b69d182faf76a9998f5ae471ea5 /top | |
| parent | 812a94dcebdaec5af30a81cfb882d8475c19b456 (diff) | |
| download | gnulib-e45d5577595787311accf5b60edf23ad58476f23.tar.gz | |
README-release: various improvements
Diffstat (limited to 'top')
| -rw-r--r-- | top/README-release | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/top/README-release b/top/README-release index 25e1dbf0cd..626777ec5b 100644 --- a/top/README-release +++ b/top/README-release @@ -15,17 +15,17 @@ Here are most of the steps we (maintainers) follow when making a release. git checkout master; git diff -* Ensure that you've pushed all changes that belong in the release - and that the NixOS/Hydra autobuilder is reporting all is well: +* Ensure that you've pushed all changes that belong in the release: + "git push origin master". + +* Check that the NixOS/Hydra autobuilder is reporting all is well: http://hydra.nixos.org/jobset/gnu/@PACKAGE@-master * Run "./bootstrap && ./configure". This downloads any new translations. -* Pre-release testing: - Ensure that "make check syntax-check" succeeds. - -* Run "make distcheck" +* Pre-release testing: ensure that "make check syntax-check distcheck" + succeeds. * Set the date, version number, and release type [stable/alpha/beta] on line 3 of NEWS, commit that, and tag the release by running e.g., @@ -49,7 +49,7 @@ 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 stable" run above. +* Run the gnupload command that was suggested by your "make TYPE" run above. * 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 @@ -60,12 +60,12 @@ Once all the builds and tests have passed, v=$(cat .prev-version) git push origin master tag v$v -* Announce it on Savannah first, so you can include the preferable - savannah.org announcement link in the email message. +* Announce it on Savannah first, so you can include the savannah.org + announcement link in the email message. From here: https://savannah.gnu.org/projects/@PACKAGE@/ - click on the "submit news", then write something like the following: + click on "submit news", then write something like the following: (If there is no such button, then enable "News" for the project via the Main -> "Select Features" menu item, or via this link: https://savannah.gnu.org/project/admin/editgroupfeatures.php?group=@PACKAGE@) |