Author: buildbot
Date: Fri Apr 12 20:45:13 2013
New Revision: 858266
Log:
Staging update by buildbot for openjpa
Modified:
websites/staging/openjpa/trunk/content/ (props changed)
websites/staging/openjpa/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).html
websites/staging/openjpa/trunk/content/release-setup.html
Propchange: websites/staging/openjpa/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Apr 12 20:45:13 2013
@@ -1 +1 @@
-1467456
+1467457
Modified:
websites/staging/openjpa/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).html
==============================================================================
---
websites/staging/openjpa/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).html
(original)
+++
websites/staging/openjpa/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).html
Fri Apr 12 20:45:13 2013
@@ -473,7 +473,7 @@ Different arguments and steps are requir
<li><a
href="http://incubator.apache.org/guides/releasemanagement.html";>http://incubator.apache.org/guides/releasemanagement.html</a></li>
</ol>
</li>
-<li>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
- <a href="*recovering-from-a-vetoed-release.html">*Recovering from a vetoed
release</a></li>
+<li>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
- <a href="#recoverFromVetoRelease">Recovering from a vetoed release</a></li>
<li>
<p>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 -</p>
<ol>
@@ -571,7 +571,7 @@ Different arguments and steps are requir
<li>
<p>Update wiki pages</p>
<ol>
-<li>After the distribution and build files have been mirrored out to the
external sites (takes about an hour), update the <a
href="/downloads.html">Downloads</a> and <a
href="/documentation.html">Documentation</a> pages with the new release.</li>
+<li>After the distribution and build files have been mirrored out to the
external sites (takes about an hour), update the <a
href="downloads.html">Downloads</a> and <a
href="documentation.html">Documentation</a> pages with the new release.</li>
<li>Make a blog announcement on the OpenJPA wiki. <ol>
<li>FIX ME!</li>
</ol>
@@ -582,17 +582,22 @@ Different arguments and steps are requir
<p>Announcing the release</p>
<ol>
<li>
-<p>FIX MEEEE After the Maven mirrors have had time to update (24 hours to be
on the safe side) and the wiki updates have been exported and mirrored to the
external website, then it's time to announce the release. Make an announcement
about the release on the dev@, user@ and [mailto:[email protected]] list as
per [the Apache Announcement Mailing Lists
page|http://www.apache.org/foundation/mailinglists.html*foundation-announce]
+<p>FIX MEEEE!! After the Maven mirrors have had time to update (24 hours to
be on the safe side) and the wiki updates have
+been exported and mirrored to the external website, then it's time to announce
the release. Make an announcement about
+the release on the dev@, user@ and [mailto:[email protected]] list as per
+<a
href="http://www.apache.org/foundation/mailinglists.html#foundation-announce";>the
Apache Announcement Mailing Lists page</a>
)</p>
-<p><span class="note">
+<p><div class="note">
Make sure you send the announcement to [email protected] from your
[email protected]. This can be achieved using gmail by setting the "From"
field to [email protected] instead of [email protected] when sending the
-announcement.</span></p>
+announcement.
+</div></p>
</li>
</ol>
</li>
</ol>
+<p><a name="recoverFromVetoRelease"></a> </p>
<h1 id="recovering-from-a-vetoed-release">Recovering from a vetoed release</h1>
<ol>
<li>
Modified: websites/staging/openjpa/trunk/content/release-setup.html
==============================================================================
--- websites/staging/openjpa/trunk/content/release-setup.html (original)
+++ websites/staging/openjpa/trunk/content/release-setup.html Fri Apr 12
20:45:13 2013
@@ -149,7 +149,8 @@ limitations under the License.
<p>These setup steps only need to be performed on a particular machine
once.</p>
<table class="info"><tr>
<td valign="top"><img src="images/information.gif" width="16" height="16"
border="0">
- <td>Developers using Linux workstations can skip over the references to
Cygwin. If using Windows, install cygwin, including **Utils/gnupg** and
**Net/openssh** packages.
+ <td>Developers using Linux workstations can skip over the references to
Cygwin. If using Windows, install cygwin, including <b>Utils/gnupg</b> and
<b>Net/openssh</b> packages.<br/><br/>
+ See <a href="http://www.gnupg.org/gph/en/manual.html";>GNU Privacy
Handbook</a> for a quick start on the basic concepts.
</tr></table>
<p><a name="ReleaseSetup-CreateandinstallaSSHkey"></a></p>
@@ -210,8 +211,8 @@ limitations under the License.
<td></p>
</li>
<li>
-<p>Each public key in the {{authorized_keys}} spans only one line. For
example:</p>
-<div class="codehilite"><pre> <span class="s">"{{ssh-dss
AAAAB3NzaC1kc3MAAA ..... agBmmfZ9uAbSqA== dsa-key-20071107}}"</span>
+<p>Each public key in the <strong><code>authorized_keys</code></strong><a
name="ReleaseSetup-CreateandinstallaSSHkey"></a> spans only one line. For
example:</p>
+<div class="codehilite"><pre> <span class="s">"ssh-dss
AAAAB3NzaC1kc3MAAA ..... agBmmfZ9uAbSqA== dsa-key-20071107"</span>
</pre></div>
@@ -321,8 +322,8 @@ limitations under the License.
<p>Backup your cygwin home directory to another media</p>
</li>
<li>
-<p>Append your public key to {{<a
href="https://svn.apache.org/repos/asf/openjpa/KEYS";>https://svn.apache.org/repos/asf/openjpa/KEYS</a>
-}} and <a
href="http://www.apache.org/dist/openjpa/KEYS";>http://www.apache.org/dist/openjpa/KEYS</a>.
See the commands describe at the beginning of this KEYS file to perform this
task. The gpg key-pair is used to sign the published artifacts for the
releases.</p>
+<p>Append your public key to <a
href="https://svn.apache.org/repos/asf/openjpa/KEYS";>https://svn.apache.org/repos/asf/openjpa/KEYS</a>
+ and <a
href="http://www.apache.org/dist/openjpa/KEYS";>http://www.apache.org/dist/openjpa/KEYS</a>.
See the commands describe at the beginning of this KEYS file to perform this
task. The gpg key-pair is used to sign the published artifacts for the
releases.</p>
<div class="codehilite"><pre><span class="nv">$</span> <span
class="err">(</span> <span class="nv">gpg</span> <span class="o">--</span><span
class="n">list</span><span class="o">-</span><span class="n">sigs</span> <span
class="o"><</span><span class="n">Real</span> <span
class="n">Name</span><span class="o">></span> <span
class="o">&&</span> <span class="n">gpg</span> <span
class="o">--</span><span class="n">armor</span> <span class="o">--</span><span
class="n">export</span> <span class="o"><</span><span class="n">Real</span>
<span class="n">Name</span><span class="o">></span> <span class="p">)</span>
<span class="o">>></span> <span class="n">KEYS</span>
</pre></div>
@@ -332,7 +333,7 @@ limitations under the License.
<td></p>
<ul>
<li>
-<p>The {{<a
href="https://svn.apache.org/repos/asf/openjpa/KEYS";>https://svn.apache.org/repos/asf/openjpa/KEYS</a>
}} file is updated via normal svn commit procedures.</p>
+<p>The <a
href="https://svn.apache.org/repos/asf/openjpa/KEYS";>https://svn.apache.org/repos/asf/openjpa/KEYS</a>
file is updated via normal svn commit procedures.</p>
<div class="codehilite"><pre><span class="n">svn</span> <span
class="n">co</span> <span class="n">https:</span><span
class="sr">//s</span><span class="n">vn</span><span class="o">.</span><span
class="n">apache</span><span class="o">.</span><span class="n">org</span><span
class="sr">/repos/</span><span class="n">asf</span><span
class="o">/</span><span class="n">openjpa</span> <span class="o">--</span><span
class="n">depth</span> <span class="n">empty</span>
<span class="n">cd</span> <span class="n">openjpa</span>
<span class="n">svn</span> <span class="n">up</span> <span
class="n">KEYS</span>
