projects
/
gnulib.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
812a94d
)
README-release: various improvements
author
Reuben Thomas
<rrt@sc3d.org>
Thu, 9 Feb 2012 13:05:57 +0000
(13:05 +0000)
committer
Jim Meyering
<meyering@redhat.com>
Sat, 11 Feb 2012 09:42:43 +0000
(10:42 +0100)
ChangeLog
patch
|
blob
|
history
top/README-release
patch
|
blob
|
history
diff --git
a/ChangeLog
b/ChangeLog
index
4fb6431
..
5d6a9a6
100644
(file)
--- a/
ChangeLog
+++ b/
ChangeLog
@@
-1,3
+1,10
@@
+2011-12-19 Reuben Thomas <rrt@sc3d.org>
+
+ README-release: various improvements
+ * top/README-release: Give a command to push changes for the
+ release. Add "distcheck" to list of other pre-release checks.
+ Fix instance of "make stable" which should be "make TYPE".
+
2012-02-09 Paul Eggert <eggert@cs.ucla.edu>
maint: replace FSF snail-mail addresses with URLs
2012-02-09 Paul Eggert <eggert@cs.ucla.edu>
maint: replace FSF snail-mail addresses with URLs
diff --git
a/top/README-release
b/top/README-release
index
25e1dbf
..
626777e
100644
(file)
--- 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
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.
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.,
* 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,
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
* 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
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@/
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@)
(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@)