Reorder a couple of steps in README-release

[Reuben Thomas]

The attached patch simply moves a paragraph so that the step of
pushing the final (NEWS-updating) commits to git happens before
uploading any release files.

>From a53f102b0d7cc8dd8db6a632321ba8b623e56f58 Mon Sep 17 00:00:00 2001
From: Reuben Thomas <address@hidden>
Date: Fri, 13 Jul 2012 11:56:10 +0100
Subject: [PATCH 2/2] README-release: reorder some steps

* top/README-release: push NEWS changes before uploading release
---
 ChangeLog          |    5 +++++
 top/README-release |   10 +++++-----
 2 files changed, 10 insertions(+), 5 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 097c90d..fe11a49 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2012-07-13  Reuben Thomas  <address@hidden>
+
+       README-release: reorder some steps
+       * top/README-release: push NEWS changes before uploading release
+
 2012-07-11  Jim Meyering  <address@hidden>
 
        maint: enable the sc_avoid_if_before_free syntax-check rule
diff --git a/top/README-release b/top/README-release
index 15110d4..453b3a7 100644
--- a/top/README-release
+++ b/top/README-release
@@ -58,17 +58,17 @@ Here are most of the steps we (maintainers) follow when 
making a release.
 
 Once all the builds and tests have passed,
 
+* Push the NEWS-updating changes and the new tag:
+
+    v=$(cat .prev-version)
+    git push origin master tag v$v
+
 * 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
   that they're all valid.
 
-* Push the NEWS-updating changes and the new tag:
-
-    v=$(cat .prev-version)
-    git push origin master tag v$v
-
 * Announce it on Savannah first, so you can include the savannah.org
   announcement link in the email message.
 
-- 
1.7.9.5



-- 
http://rrt.sc3d.org/