ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ma...@apache.org
Subject svn commit: r1375945 - /ace/site/trunk/content/dev-doc/release-guide.mdtext
Date Wed, 22 Aug 2012 08:44:24 GMT
Author: marrs
Date: Wed Aug 22 08:44:23 2012
New Revision: 1375945

URL: http://svn.apache.org/viewvc?rev=1375945&view=rev
Log:
Updated the release guide after getting some review comments by Karl.

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=1375945&r1=1375944&r2=1375945&view=diff
==============================================================================
--- ace/site/trunk/content/dev-doc/release-guide.mdtext (original)
+++ ace/site/trunk/content/dev-doc/release-guide.mdtext Wed Aug 22 08:44:23 2012
@@ -22,20 +22,20 @@ Before you can start staging a release c
 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-1.0.0 ace-sources-1.0.0
+	$ svn co https://svn.apache.org/repos/asf/ace/tags/ace-sources-X.Y.Z ace-sources-X.Y.Z
 
 The next step is to create the source archive:
 
 	:::sh
-	$ cd build
+	$ cd ace-sources-X.Y.Z/build
 	$ ant -f src-build.xml package-src
 
-Then you sign the source archive, and create md5 and sha1 signatures for it:
+Then you sign the source archive by invoking the following target:
 
 	:::sh
 	$ ant -f src-build.xml sign-src
 
-Now you can upload the source archive and the signatures to our development area, which we
use to stage this release candidate. This can be done via "svnpubsub":
+Now you can upload the source archive and the signatures to our development area, which we
use to stage this release candidate. This development area can be found at https://dist.apache.org/repos/dist/dev/ace
and adding files to it can be done using "svnpubsub" which is taken care of by the following
target:
 
 	:::sh
 	$ ant -f src-build.xml commit-to-staging
@@ -48,6 +48,10 @@ Start a vote on the dev@ace.apache.org l
 	To: "Apache ACE developers list" <dev@ace.apache.org>
 	Subject: [VOTE] Release ACE version X.Y.Z
 	
+	The source code of Apache ACE version X.Y.Z is available in our
+	staging area here:
+	https://dist.apache.org/repos/dist/dev/ace/ace-sources-X.Y.Z
+	
 	Please vote to approve this release:
 	[  ] +1 Approve the release
 	[  ] -1 Veto the release (please motivate)
@@ -74,15 +78,15 @@ And, depending on the result, continue w
 
 ## Promoting the release
 
-Move the artifacts from the development area to the final release location:
+Move the artifacts from the development area to the final release location at https://dist.apache.org/repos/dist/release/ace
by invoking the following target:
 
 	:::sh
 	$ ant -f src-build.xml promote-to-release
 
-Then update the tag in subversion, for example for the 1.0.0 release like this:
+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-1.0.0 https://svn.apache.org/repos/asf/ace/releases/ace-sources-1.0.0
-m "Apache ACE source release 1.0.0 tagged."
+	$ 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 source 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:
 



Mime
View raw message