Author: marrs
Date: Tue Apr 23 15:27:46 2013
New Revision: 1471009
URL: http://svn.apache.org/r1471009
Log:
Updated the release guide.
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=1471009&r1=1471008&r2=1471009&view=diff
==============================================================================
--- ace/site/trunk/content/dev-doc/release-guide.mdtext (original)
+++ ace/site/trunk/content/dev-doc/release-guide.mdtext Tue Apr 23 15:27:46 2013
@@ -15,6 +15,7 @@ To create a release you must:
Before you can start staging a release candidate, you must:
* Make sure there are no snapshot dependencies anymore.
+* Double check that the version you want to create is correctly filled in in
build/build.xml.
* Create a tagged version of the sources in preparation of the release
candidate.
## Staging a release candidate
@@ -24,21 +25,21 @@ Staging a release starts by checking out
:::sh
$ 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:
+The next step is to create the archives:
:::sh
$ cd ace-sources-X.Y.Z/build
- $ ant -f src-build.xml package-src
+ $ ant package
-Then you sign the source archive by invoking the following target:
+Then you sign archives by invoking the following target:
:::sh
- $ ant -f src-build.xml sign-src
+ $ ant sign
-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:
+Now you can upload the archives 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
+ $ ant commit-to-staging
## Voting on the release
@@ -48,9 +49,11 @@ Start a vote on the [email protected] l
To: "Apache ACE developers list" <[email protected]>
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
+ The source code of Apache ACE version X.Y.Z is available,
+ along with an archive containing all dependencies and a
+ binary release for convenience. They can all be found in
+ our staging area here:
+ https://dist.apache.org/repos/dist/dev/ace/
Please vote to approve this release:
[ ] +1 Approve the release
@@ -81,12 +84,12 @@ And, depending on the result, continue w
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
+ $ 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
source release X.Y.Z 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
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:
@@ -104,6 +107,6 @@ Now wait at least 24 hours to allow the
Remove the artifacts from the development area:
:::sh
- $ ant -f src-build.xml delete-from-staging
+ $ ant delete-from-staging
We keep the tag in subversion for reference.
