svn commit: r1588277 - /ace/site/trunk/content/dev-doc/release-guide.mdtext

[ma...@apache.org]

Author: marrs
Date: Thu Apr 17 15:13:14 2014
New Revision: 1588277

URL: http://svn.apache.org/r1588277
Log:
Small updates to the release guide to better align with the 2.0.1 release I just staged.

Modified:
    ace/site/trunk/content/dev-doc/release-guide.mdtext

Modified: ace/site/trunk/content/dev-doc/release-guide.mdtext
URL: http://svn.apache.org/viewvc/ace/site/trunk/content/dev-doc/release-guide.mdtext?rev=1588277&r1=1588276&r2=1588277&view=diff
==============================================================================
--- ace/site/trunk/content/dev-doc/release-guide.mdtext (original)
+++ ace/site/trunk/content/dev-doc/release-guide.mdtext Thu Apr 17 15:13:14 2014
@@ -17,21 +17,24 @@ To create a release you *must*:
 
 Before you can start staging a release candidate, you must:
 
-* Make sure there are no dependencies on snapshots/unreleased versions;
+* make sure there are no dependencies on snapshots/unreleased versions;
 * double check that the version you want to create is correctly filled in in <tt>build/build.xml</tt>;
-* create a tagged version of the sources in preparation of the release candidate.
+* create a tagged version of the sources in preparation of the release candidate:
+
+	::sh
+	svn copy https://svn.apache.org/repos/asf/ace/trunk/ https://svn.apache.org/repos/asf/ace/releases/X.Y.Z -m "Release X.Y.Z"
 
 ## Staging a release candidate
 
 Staging a release starts by checking out a tagged version of the sources:
 
 	:::sh
-	$ svn co https://svn.apache.org/repos/asf/ace/tags/ace-sources-X.Y.Z ace-sources-X.Y.Z
+	$ svn co https://svn.apache.org/repos/asf/ace/releases/X.Y.Z ace-X.Y.Z
 
 The next step is to build the software and create the archives:
 
 	:::sh
-	$ cd ace-sources-X.Y.Z/build
+	$ cd ace-X.Y.Z/build
 	$ ant
 	$ ant package
 
@@ -53,7 +56,6 @@ be done using "svnpubsub" which is taken
 Start a vote on the dev@ace.apache.org list, for example (be sure to replace
 <tt>X.Y.Z</tt> with the *correct* version!):
 
-	:::sh
 	To: "Apache ACE developers list" <de...@ace.apache.org>
 	Subject: [VOTE] Release ACE version X.Y.Z
 	
@@ -111,11 +113,6 @@ following target:
 	:::sh
 	$ ant promote-to-release
 
-Then update the tag in subversion, for example for the *X.Y.Z* release like this:
-
-	:::sh
-	$ svn move https://svn.apache.org/repos/asf/ace/tags/ace-sources-X.Y.Z https://svn.apache.org/repos/asf/ace/releases/ace-sources-X.Y.Z -m "Apache ACE release X.Y.Z tagged."
-
 Now wait at least 24 hours to allow the release to be properly mirrored and
 then update the news and download page on the Apache ACE website and announce
 the release:
@@ -128,6 +125,10 @@ the release:
 	This release is available from our download page at:
 	http://ace.apache.org/downloads.html
 
+After announcing the release, please update the baseline bundles contained in
+trunk/cnf/releaserepo based on the released artifacts (remove old versions, keep
+only the latest one).
+
 
 ## Cancelling the release