Author: buildbot
Date: Thu May 15 16:29:46 2014
New Revision: 908925
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
Propchange: websites/staging/openjpa/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu May 15 16:29:46 2014
@@ -1 +1 @@
-1594763
+1594968
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
Thu May 15 16:29:46 2014
@@ -149,7 +149,7 @@ limitations under the License.
<h1 id="release-steps-for-openjpa-12x-2x">Release Steps for OpenJPA 1.2.x -
2.x</h1>
<p>We're starting to move our builds over to using the Apache Nexus repository
(repository.apache.org) for releasing SNAPSHOT and release artifacts.
More details on releasing artifacts and using Nexus can be found on the Maven
website at - <a
href="http://maven.apache.org/developers/release/apache-release.html";>http://maven.apache.org/developers/release/apache-release.html</a></p>
-<ol>
+<ul>
<li>
<p>Environment setup for releasing artifacts (same for SNAPSHOTs and
releases)</p>
<ol>
@@ -661,13 +661,19 @@ $ <span class="n">rm</span> <span class=
</ul>
</li>
<li>
-<p>If new branch is created, one will need to submit a request to
infrastructure team to create a new buildbot doc build process for the new
branch. See <a
href="http://openjpa.apache.org/buildbot.tips.n.techniques.html";>BuildBot Doc
Build</a> for tips.</p>
+<p>If new branch is created, one will need to submit requests to
infrastructure team to create or update the buildbot process for the new
branch. See <a
href="http://openjpa.apache.org/buildbot.tips.n.techniques.html";>BuildBot Doc
Build</a> for doc build tips, see the <a
href="http://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson";>Jenkins
wiki</a> for information on the Jenkins build process. Also, reference the
following JIRAs for learning further about the process.</p>
+</li>
+<li>
+<p>Example <a href="https://issues.apache.org/jira/browse/INFRA-7738";>doc
builds JIRA</a></p>
+</li>
+<li>
+<p>Example <a href="https://issues.apache.org/jira/browse/INFRA-7739";>Jenkins
build JIRA</a> </p>
</li>
<li>
<p>Update the <a href="http://openjpa.apache.org/downloads.html";>Downloads</a>
wiki page:</p>
<ul>
<li>Add the newly ${RELEASE} binary and source links to the dynamic
distributed servers</li>
-<li>Add the newly ${RELEASE} RELEASE.NOTE.html link.</li>
+<li>Add the newly ${RELEASE} RELEASE-NOTES.html link.</li>
<li>Update previous release links to the corresponding entry in
//archive.apache.org/dist/openjpa/* </li>
</ul>
</li>
@@ -702,13 +708,13 @@ the release on the dev@, user@ and [mail
<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
+field to [email protected] instead of [email protected] when sending the
announcement.
</div></p>
</li>
</ol>
</li>
-</ol>
+</ul>
<p><a name="recoverFromVetoRelease"></a> </p>
<h1 id="recovering-from-a-vetoed-release">Recovering from a vetoed release</h1>
<ol>
