Author: mfranklin
Date: Tue Jul 9 13:57:13 2013
New Revision: 1501265
URL: http://svn.apache.org/r1501265
Log:
Updated release documentation to support scripted releases.
Modified:
rave/site/trunk/content/release-process.mdtext
Modified: rave/site/trunk/content/release-process.mdtext
URL:
http://svn.apache.org/viewvc/rave/site/trunk/content/release-process.mdtext?rev=1501265&r1=1501264&r2=1501265&view=diff
==============================================================================
--- rave/site/trunk/content/release-process.mdtext (original)
+++ rave/site/trunk/content/release-process.mdtext Tue Jul 9 13:57:13 2013
@@ -21,6 +21,8 @@ There are two distinct sets of artifacts
All of the steps below apply to both the master and project releases, unless
otherwise specified. As an alternative to releasing separately, the projects
MAY be released together as one combined release. The steps for this can be
found below. ([Combined Release Steps](#combined))
+Additionally, most of the steps in the release process can be automated using
the release scripts found in the
[repository](http://svn.apache.org/repos/asf/rave/release-management/). Steps
for the release scripts are found below. ([Scripted Release Steps](#scripted)).
+
####Common Release Steps
1. Environment setup for releasing artifacts (same for SNAPSHOTs and releases)
@@ -234,4 +236,23 @@ In order to perform a combined release o
* Build the rave-master FIRST
* When prompted to change the rave-project dependency on rave-master
SNAPSHOT, do so to the release that you just built
* Execute the remaining steps using the following e-mail templates
- * [PMC Release Vote](PPMC_Combined.txt)
\ No newline at end of file
+ * [PMC Release Vote](PPMC_Combined.txt)
+
+<a name="scripted" />
+####Scripted Release
+There are two scripts in the repository created to facilitate simpler
releases: release.sh & publish.sh. The release script handles steps up to the
VOTE e-mails and the publish script handles publishing the artifacts to the
mirrors once a successful vote has been achieved.
+
+To use the scripts, do the following:
+
+1. Export release.sh to a temporary directory
+2. Execute `./release.sh ${project.version} /Absolute/Path/To/Apache/SSH/Key`
+3. When prompted, provide the same responses that you would in step 5 of the
release steps above. Note that the submodules are autoversioned, so you should
only need to input the release version once.
+4. After a successful execution follow steps 10 & 12
+
+After a successful vote, do the following:
+
+1. Execute step 12.1 from the above list
+2. Export publish.sh to a temporary directory
+3. Execute `./publish.sh ${project.name} ${project.version}
/Absolute/Path/To/Apache/SSH/Key`
+4. Execute steps 12.4-15
+
\ No newline at end of file
