Return-Path: 
 <commits-return-20073-apmail-subversion-commits-archive=subversion.apache.org@subversion.apache.org>
X-Original-To: apmail-subversion-commits-archive@minotaur.apache.org
Delivered-To: apmail-subversion-commits-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 625579CCB
	for <apmail-subversion-commits-archive@minotaur.apache.org>;
 Thu, 12 Apr 2012 11:11:03 +0000 (UTC)
Received: (qmail 72630 invoked by uid 500); 12 Apr 2012 11:11:03 -0000
Delivered-To: apmail-subversion-commits-archive@subversion.apache.org
Received: (qmail 72555 invoked by uid 500); 12 Apr 2012 11:11:03 -0000
Mailing-List: contact commits-help@subversion.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@subversion.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@subversion.apache.org>
List-Post: <mailto:commits@subversion.apache.org>
List-Id: <commits.subversion.apache.org>
Reply-To: dev@subversion.apache.org
Delivered-To: mailing list commits@subversion.apache.org
Received: (qmail 72547 invoked by uid 99); 12 Apr 2012 11:11:03 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Apr 2012 11:11:03 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Apr 2012 11:11:00 +0000
Received: from eris.apache.org (localhost [127.0.0.1])
	by eris.apache.org (Postfix) with ESMTP id 75E07238897A;
	Thu, 12 Apr 2012 11:10:39 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r1325205 -
 /subversion/site/publish/docs/community-guide/releasing.part.html
Date: Thu, 12 Apr 2012 11:10:39 -0000
To: commits@subversion.apache.org
From: stsp@apache.org
X-Mailer: svnmailer-1.0.8-patched
Message-Id: <20120412111039.75E07238897A@eris.apache.org>

Author: stsp
Date: Thu Apr 12 11:10:38 2012
New Revision: 1325205

URL: http://svn.apache.org/viewvc?rev=1325205&view=rev
Log:
* site/publish/docs/community-guide/releasing.part.html: It makes more
   sense to update the website before sending the release announcement,
   not after. So swap the corresponding sections.

Modified:
    subversion/site/publish/docs/community-guide/releasing.part.html

Modified: subversion/site/publish/docs/community-guide/releasing.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=1325205&r1=1325204&r2=1325205&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Thu Apr 12 11:10:38 2012
@@ -993,29 +993,6 @@ releases using <tt>release.py clean-dist
 <p>It is then time for the release manager to go and enjoy his
 $favorite_beverage.</p>
 
-<div class="h4" id="releasing-announce">
-<h4>Announcing the release
-  <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#releasing-announce"
-    title="Link to this section">&para;</a>
-</h4>
-
-<p>Write a release announcement, referring to previous ones for
-guidance.  Remember to include the URL and SHA1 checksums in the
-announcement!  The <tt>release.py write-announcement</tt> subcommand
-creates a template announcement which can be customized for specific
-circumstances.</p>
-
-<p>Send the announcement to dev@, users@, and announce@ lists, from your
-@apache.org email address.  (Mail to announce@ will bounce if sent from any
-other address.)  Ensure that your mailer doesn't wrap the URLs over multiple
-lines.  The mail to announce@subversion.apache.org will also be forwarded to
-announce@apache.org.</p>
-
-<p>Update the topics in various Subversion-related IRC channels, such as
-<tt>#svn</tt> and <tt>#svn-dev</tt> on freenode.</p>
-
-</div> <!-- release-announce -->
-
 <div class="h4" id="releasing-update-website">
 <h4>Update the website
   <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#"releasing-update-website
@@ -1051,6 +1028,29 @@ announce@apache.org.</p>
 
 </div> <!-- release-update-website -->
 
+<div class="h4" id="releasing-announce">
+<h4>Announcing the release
+  <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#releasing-announce"
+    title="Link to this section">&para;</a>
+</h4>
+
+<p>Write a release announcement, referring to previous ones for
+guidance.  Remember to include the URL and SHA1 checksums in the
+announcement!  The <tt>release.py write-announcement</tt> subcommand
+creates a template announcement which can be customized for specific
+circumstances.</p>
+
+<p>Send the announcement to dev@, users@, and announce@ lists, from your
+@apache.org email address.  (Mail to announce@ will bounce if sent from any
+other address.)  Ensure that your mailer doesn't wrap the URLs over multiple
+lines.  The mail to announce@subversion.apache.org will also be forwarded to
+announce@apache.org.</p>
+
+<p>Update the topics in various Subversion-related IRC channels, such as
+<tt>#svn</tt> and <tt>#svn-dev</tt> on freenode.</p>
+
+</div> <!-- release-announce -->
+
 </div> <!-- releasing-release -->
 
 </div> <!-- release-creating -->