maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r877971 - in /websites/staging/maven/trunk/content: ./ developers/release/maven-core-release.html maven-site-1.0-site.jar
Date Tue, 10 Sep 2013 21:35:15 GMT
Author: buildbot
Date: Tue Sep 10 21:35:14 2013
New Revision: 877971

Staging update by buildbot for maven

    websites/staging/maven/trunk/content/   (props changed)

Propchange: websites/staging/maven/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Tue Sep 10 21:35:14 2013
@@ -1 +1 @@

Modified: websites/staging/maven/trunk/content/developers/release/maven-core-release.html
--- websites/staging/maven/trunk/content/developers/release/maven-core-release.html (original)
+++ websites/staging/maven/trunk/content/developers/release/maven-core-release.html Tue Sep
10 21:35:14 2013
@@ -241,8 +241,8 @@ Olivier Lamy" />
       <div id="contentBox">
         <!-- Licensed to the Apache Software Foundation (ASF) under one --><!--
or more contributor license agreements.  See the NOTICE file --><!-- distributed with
this work for additional information --><!-- regarding copyright ownership.  The ASF
licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!--
"License"); you may not use this file except in compliance --><!-- with the License.
 You may obtain a copy of the License at --><!--  --><!--
--><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!--
software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License
for the --><!-- specific language governing permissions and limitations --><!--
under the License. --><div class="section">
 <h2>Releasing Maven<a name="Releasing_Maven"></a></h2>
-<p>Maven differs slightly in its release process due to several extra steps and this
need to be publish via Apache svnpubsub.</p>
-<p>The goal is to commit candidate release to svn tree$VERSION.
Then once the vote passed svn move to$VERSION.</p>
+<p>Maven differs slightly in its release process due to several extra steps.</p>
+<p>The goal is to commit candidate release to svn tree <a class="externalLink" href=""></a>/$VERSION.
Then once the vote passed, svn move to <a class="externalLink" href=""></a>/$VERSION.</p>
 <p>The tree directory is:</p>
@@ -267,7 +267,7 @@ Olivier Lamy" />
 <p>Below describes the additional steps that need to be taken at the points where the
website are updated in those instructions.</p>
 <div class="section">
 <h4>Update the DOAP Information<a name="Update_the_DOAP_Information"></a></h4>
-<p>Edit <a class="externalLink" href=""></a>
to list the new release.</p></div>
+<p>Edit <a class="externalLink" href=""></a>
to list the new release.</p></div>
 <div class="section">
 <h4>Update the Release Notes and Web Site<a name="Update_the_Release_Notes_and_Web_Site"></a></h4>
 <p>Checkout <a class="externalLink" href=""></a>.</p>
@@ -281,36 +281,30 @@ Olivier Lamy" />
 <li>create docs/$version</li>
 <li>populate docs/$version/release-notes.txt from JIRA</li>
 <li>create docs/$version/release-notes.apt.vm (see other versions for an example)</li></ul>
-<p>Only deploy the site once the release is present on the mirrors, and the reference
documentation has been deployed to /ref/.</p></div>
+<p>Only deploy the site once the release is present on the mirrors, and the reference
documentation has been deployed to <a href="/ref">/ref/</a>.</p></div>
 <div class="section">
 <h4>Stage the Latest Documentation<a name="Stage_the_Latest_Documentation"></a></h4>
 <p>Once the release is prepared, but before the release vote, the site needs to be
-<ol style="list-style-type: decimal">
-<li>From the site checkout, stage the site (replacing $USER and $VERSION):
-<div class="source">
-<pre>mvn -Preporting site site:stage-deploy -DstagingSiteURL=scp://$USER/public_html/staged-sites/maven-$VERSION</pre></div>
-<p><b>Note:</b> It requires Maven 2.1.0 or higher to successfully deploy
to <tt></tt> via SSH. Older Maven versions will fail due to <tt>com.jcraft.jsch.JSchException:
Algorithm negotiation fail</tt>.</p>
-<div class="source">
-<p>Some developers have <a class="externalLink" href="">
reported problems</a> with the <tt>site:stage-deploy</tt> goal. In that
case, you can stage the site locally and upload it manually:</p>
+<p>From the release checkout, stage the site:</p>
 <div class="source">
 <pre>mvn -Preporting site site:stage
-scp -r target/staging/$USER/public_html/staged-sites/maven-$VERSION$USER/public_html/staged-sites/maven-$VERSION</pre></div></li></ol></div>
+mvn scm-publish:publish-scm</pre></div>
+<p>This will publish the site in <a href="/ref/3-LATEST">/ref/3-LATEST</a>.</p></div>
 <div class="section">
 <h4>Add New Version to ASF Distribution Directory<a name="Add_New_Version_to_ASF_Distribution_Directory"></a></h4>
-<p>In addition to promoting the repository, the release archives should be moved to
the release svnpubsub tree :</p>
-<li>svn mv$VERSION</li></ul></div>
+<p>In addition to promoting the repository, the release archives should be moved to
the release svnpubsub tree:</p>
+<div class="source">
+<pre>svn mv$VERSION</pre></div></div>
 <div class="section">
-<h4>Deploy the Current References<a name="Deploy_the_Current_References"></a></h4>
+<h4>Deploy the Current Reference<a name="Deploy_the_Current_Reference"></a></h4>
 <p>The source code references and API docs need to be deployed before deploying the
web site with the new version.</p>
-<p>This is described in <a href="../website/deploy-maven-current-ref.html"> Deploying
the Current References</a>.</p></div>
+<p>This consists in copying in website svn tree the /ref/3-LATEST directory to /ref/$VERSION.</p>
+<div class="source">
+<pre>svn cp$VERSION</pre></div></div>
 <div class="section">
 <h4>Deploying the Release Website<a name="Deploying_the_Release_Website"></a></h4>
 <p>Once both of the above have synced to the main site and a suitable number of mirrors,
proceed to update the web site and produce the announcement.</p>
-<p>Commit your changes and then deploy the main Maven site checked out earlier.</p>
-<div class="source">
-<pre>mvn -Preporting clean site-deploy</pre></div></div>
+<p>Commit your changes and then <a href="../website/deploy-maven-website.html">deploy
the main Maven site</a>.</p></div>
 <div class="section">
 <h4>Remove Old Versions from ASF Distribution Directory<a name="Remove_Old_Versions_from_ASF_Distribution_Directory"></a></h4>
 <p>Next, any superceded releases should be removed from the above locations (after
confirming that they exist in /www/</p></div>

Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
Binary files - no diff available.

View raw message