Author: buildbot
Date: Mon Apr 2 21:11:03 2012
New Revision: 811174
Log:
Staging update by buildbot for rave
Modified:
websites/staging/rave/trunk/content/ (props changed)
websites/staging/rave/trunk/content/release-process.html
Propchange: websites/staging/rave/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Apr 2 21:11:03 2012
@@ -1 +1 @@
-1308187
+1308571
Modified: websites/staging/rave/trunk/content/release-process.html
==============================================================================
--- websites/staging/rave/trunk/content/release-process.html (original)
+++ websites/staging/rave/trunk/content/release-process.html Mon Apr 2
21:11:03 2012
@@ -65,7 +65,7 @@
<div id="content">
<h1 class="title">Release Process</h1>
- <h3 id="incubator-release-steps-overview">Incubator Release Steps
Overview</h3>
+ <h3 id="release-steps-overview">Release Steps Overview</h3>
<p>There are two distinct sets of artifacts that are released on independent
schedules: rave-master & rave-project. The rave-master is the project
metadata (committers, roles, etc) and only needs to be released when there is a
change in the structure of the project itself (committers, mentors, etc). The
rave-project artifacts are comprised of all rave source code, binaries and a
standalone demo.<br />
</p>
<p>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. (<a href="#combined">Combined Release Steps</a>)</p>
@@ -95,7 +95,7 @@
<p>Prepare the source for release: <br />
</p>
<ol>
-<li>Cleanup JIRA so the Fix Version in issues resolved since the last release
includes this release version correctly. Also, transition any Resolved issues
to the Closed state.</li>
+<li>Cleanup JIRA so the Fix Version in issues resolved since the last release
includes this release version correctly. </li>
<li>Update the text files in a working copy of the project root -<ol>
<li>Update the CHANGELOG based on the Text release reports from JIRA.</li>
<li>Review and update README.txt if needed.</li>
@@ -125,7 +125,7 @@
</p>
<ul>
<li>Release version - take the default </li>
-<li>SCM release tag - <em>DO NOT TAKE THE DEFAULT</em> -: :
${project.version}-incubating</li>
+<li>SCM release tag - <em>DO NOT TAKE THE DEFAULT</em> -
${project.version}</li>
<li>New development version - take the default</li>
<li>GPG Passprhase<br />
</li>
@@ -176,7 +176,7 @@
<ul>
<li>
<p>This step will create a maven staging repository and site for use in
testing and voting. </p>
-<p>$ mvn release:perform -Papache-release -Duser.name=<your_apache_uid></p>
+<p>$ mvn release:perform -Papache-release </p>
</li>
<li>
<p><em>If your local OS userid doesn't match your Apache userid, then you'll
have to also override the value provided by the OS to Maven for the site-deploy
step to work. This is known to work for Linux, but not for Mac and unknown for
Windows.</em></p>
@@ -217,20 +217,20 @@
<ul>
<li>Checkout the tag from SVN </li>
<li>$ mvn -P dist</li>
-<li>$ gpg -ab
./rave-portal/target/rave-<em>${project.version}</em>-incubating.bin.zip</li>
-<li>$ gpg -ab
./rave-portal/target/rave-<em>${project.version}</em>-incubating.bin.tar.gz</li>
-<li>$ gpg --print-md SHA512
rave-<em>${project.version}</em>-incubating.bin.zip >
rave-<em>${project.version}</em>-incubating.bin.zip.sha</li>
-<li>$ gpg --print-md SHA512
rave-<em>${project.version}</em>-incubating.bin.tar.gz >
rave-<em>${project.version}</em>-incubating.bin.zip.sha</li>
-<li>$ gpg --print-md MD5 rave-<em>${project.version}</em>-incubating.bin.zip
> rave-<em>${project.version}</em>-incubating.bin.zip.md5</li>
-<li>$ gpg --print-md MD5
rave-<em>${project.version}</em>-incubating.bin.tar.gz >
rave-<em>${project.version}</em>-incubating.bin.zip.md5</li>
+<li>$ gpg -ab
./rave-portal/target/rave-<em>${project.version}</em>.bin.zip</li>
+<li>$ gpg -ab
./rave-portal/target/rave-<em>${project.version}</em>.bin.tar.gz</li>
+<li>$ gpg --print-md SHA512 rave-<em>${project.version}</em>.bin.zip >
rave-<em>${project.version}</em>.bin.zip.sha</li>
+<li>$ gpg --print-md SHA512 rave-<em>${project.version}</em>.bin.tar.gz >
rave-<em>${project.version}</em>.bin.zip.sha</li>
+<li>$ gpg --print-md MD5 rave-<em>${project.version}</em>.bin.zip >
rave-<em>${project.version}</em>.bin.zip.md5</li>
+<li>$ gpg --print-md MD5 rave-<em>${project.version}</em>.bin.tar.gz >
rave-<em>${project.version}</em>.bin.zip.md5</li>
</ul>
</li>
<li>
<p>Copy the artifacts to the staging area</p>
<ul>
-<li>$ ssh people.apache.org mkdir
/www/people.apache.org/builds/incubator/rave/0.1-incubating </li>
-<li>$ scp
./rave-portal/target/rave-<em>${project.version}</em>-incubating.bin.*
${user.name}@people.apache.org:/www/people.apache.org/builds/incubator/rave/${project.version}/</li>
-<li>Verify they are downloadable from
http://people.apache.org/builds/incubator/rave/0.1-incubating/</li>
+<li>$ ssh people.apache.org mkdir
/www/people.apache.org/builds/rave/${project.version}</li>
+<li>$ scp ./rave-portal/target/rave-<em>${project.version}</em>.bin.*
${user.name}@people.apache.org:/www/people.apache.org/builds/rave/${project.version}/</li>
+<li>Verify they are downloadable from
http://people.apache.org/builds/rave/${project.version}/</li>
</ul>
</li>
</ol>
@@ -238,33 +238,18 @@
<li>
<p>Put the release candidate up for a vote</p>
<ol>
-<li>Create a VOTE email thread on rave-dev@ to record votes as replies, like
<a href="release-vote.txt">this</a></li>
-<li>Create a DISCUSS email thread on rave-dev@ for any vote questions, <a
href="release-discuss.txt">this</a></li>
+<li>Create a VOTE email thread on dev@ to record votes as replies, like <a
href="release-vote.txt">this</a></li>
+<li>Create a DISCUSS email thread on dev@ for any vote questions, <a
href="release-discuss.txt">this</a></li>
<li>
<p>Perform a review of the release and cast your vote. See the following for
more details on Apache releases </p>
<p><a
href="http://www.apache.org/dev/release.html";>http://www.apache.org/dev/release.html</a><br
/>
-<a
href="http://incubator.apache.org/guides/releasemanagement.html";>http://incubator.apache.org/guides/releasemanagement.html</a></p>
+</p>
</li>
<li>
<p>A -1 vote does not necessarily mean that the vote must be redone, however
it is usually a good idea to rollback the release if a -1 vote is received. See
- Recovering from a vetoed release</p>
</li>
<li>After the vote has been open for at least 72 hours, has at least three +1
PMC votes and no -1 votes, then post the results to the vote thread by -<ul>
-<li>reply to the initial email and prepend to the original subject
"[RESULTS]"</li>
-<li>Include a list of everyone who voted +1, 0 or -1.</li>
-</ul>
-</li>
-</ol>
-</li>
-<li>
-<p>Put the release candidate up for an Incubator PMC vote</p>
-<ol>
-<li>
-<p>Create a VOTE email thread on general@incubator to record votes as replies,
like <a href="vote-ipmc.txt">this</a></p>
-</li>
-<li>
-<p>After the vote has been open for at least 72 hours, has at least three +1
Incubator PMC votes and no -1 votes, then post the results to the vote thread
by -</p>
-<ul>
-<li>replying to the initial email and prepend to the original subject
"[RESULTS]"</li>
+<li>reply to the initial email and prepend to the original subject
"[RESULT]"</li>
<li>Include a list of everyone who voted +1, 0 or -1.</li>
</ul>
</li>
@@ -288,9 +273,9 @@
</p>
<ul>
<li>$ ssh ${user.name}@people.apache.org </li>
-<li>$ mkdir /www/www.apache.org/dist/incubator/rave/${project.version} <br />
+<li>$ mkdir /www/www.apache.org/dist/rave/${project.version} <br />
</li>
-<li>$ cd /www/www.apache.org/dist/incubator/rave/${project.version} <br />
+<li>$ cd /www/www.apache.org/dist/rave/${project.version} <br />
</li>
<li>$ wget
https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-project/${project.version}/rave-project-${project.version}-source-release.zip
<br />
</li>
@@ -300,8 +285,8 @@
</li>
<li>$ wget
https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-project/${project.version}/rave-project-${project.version}-source-release.zip.sha1
<br />
</li>
-<li>$ cp -rfv
/www/people.apache.org/builds/incubator/rave/${project.version}/* ./</li>
-<li>$ rm -rfv
/www/people.apache.org/builds/incubator/rave/${project.version}</li>
+<li>$ cp -rfv /www/people.apache.org/builds/rave/${project.version}/* ./</li>
+<li>$ rm -rfv /www/people.apache.org/builds/rave/${project.version}</li>
<li>
<p>Make sure all the copied files have g+rw set and only o+r set</p>
<p>$ find . -user ${user.name} -type f | xargs chmod 664<br />
@@ -316,12 +301,12 @@
</ol>
</li>
<li>
-<p>Update the JIRA versions page to mark the version as "released", and set
the date to the date that the release was approved. You may also need to make a
new release entry for the next release.</p>
+<p>Update the JIRA versions page to close all issues, mark the version as
"released", and set the date to the date that the release was approved. You may
also need to make a new release entry for the next release.</p>
</li>
<li>Announcing the release</li>
<li>After the mirrors have had time to update (24 hours to be on the safe
side) update the wiki with pointers to the new release</li>
<li>Make a news announcement on the Rave homepage.</li>
-<li>Make an announcement about the release on the
[email protected], [email protected],
[email protected], and [email protected] list as per the Apache
Announcement Mailing Lists page)</li>
+<li>Make an announcement about the release on the [email protected],
[email protected], and [email protected] list as per the Apache
Announcement Mailing Lists page)</li>
</ol>
<h4 id="recovering-from-a-vetoed-release">Recovering from a vetoed release</h4>
<ol>
@@ -331,14 +316,14 @@
</li>
<li>
<p>Delete the svn tag created by the release:perform step -</p>
-<p>$ svn del https://svn.apache.org/repos/asf/rave/tags/0.1-incubating -m
"deleting tag from rolled back release"</p>
+<p>$ svn del https://svn.apache.org/repos/asf/rave/tags/${project.version} -m
"deleting tag from rolled back release"</p>
</li>
<li>
<p>Delete the build artifacts on people & www <br />
</p>
<ul>
-<li>$ rm -rfv
/www/people.apache.org/builds/incubator/rave/${project.version}</li>
-<li>$ rm -rfv /www/www.apache.org/dist/incubator/rave/${project.version}</li>
+<li>$ rm -rfv /www/people.apache.org/builds/rave/${project.version}</li>
+<li>$ rm -rfv /www/www.apache.org/dist/rave/${project.version}</li>
</ul>
</li>
<li>
@@ -384,9 +369,8 @@ gpg: Signature made ...</p>
</li>
<li>Execute the remaining steps using the following e-mail templates<br />
<ul>
-<li><a href="PPMC_Combined.txt">PPMC Release Vote</a><br />
+<li><a href="PPMC_Combined.txt">PMC Release Vote</a><br />
</li>
-<li><a href="IPMC_Combined.txt">IMPC Release Vote</a></li>
</ul>
</li>
</ul>
