Author: buildbot
Date: Wed Nov 11 18:34:27 2015
New Revision: 972127
Log:
Staging update by buildbot for felix
Modified:
websites/staging/felix/trunk/content/ (props changed)
websites/staging/felix/trunk/content/documentation/development/release-management-nexus.html
Propchange: websites/staging/felix/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Nov 11 18:34:27 2015
@@ -1 +1 @@
-1713666
+1713908
Modified:
websites/staging/felix/trunk/content/documentation/development/release-management-nexus.html
==============================================================================
---
websites/staging/felix/trunk/content/documentation/development/release-management-nexus.html
(original)
+++
websites/staging/felix/trunk/content/documentation/development/release-management-nexus.html
Wed Nov 11 18:34:27 2015
@@ -18,7 +18,7 @@
limitations under the License.
-->
<head>
- <title>Apache Felix - Release Management (Nexus)</title>
+ <title>Apache Felix - Release Management</title>
<link rel="icon" href="/res/favicon.ico">
<link rel="stylesheet" href="/res/site.css" type="text/css" media="all">
<link rel="stylesheet" href="/res/codehilite.css" type="text/css"
media="all">
@@ -76,7 +76,7 @@ h2:hover > .headerlink, h3:hover > .head
<a href="/">Home</a> » <a
href="/documentation.html">Documentation</a> » <a
href="/documentation/development.html">Development</a>
</div>
- <h1>Release Management (Nexus)</h1>
+ <h1>Release Management</h1>
<style type="text/css">
/* The following code is added by mdx_elementid.py
It was originally lifted from http://subversion.apache.org/style/site.css */
@@ -188,10 +188,17 @@ the released version.
</li>
<li>Verify the staged artifacts<ul>
<li>if you click on your repository, a tree view will appear below. You can
then browse the contents to ensure the artifacts are as you expect them. Pay
particular attention to the existence of *.asc (signature) files. If you don't
like the content of the repository, right click your repository and choose
<em>Drop</em>. You can then rollback your release (see <em>Canceling the
Release</em>) and repeat the process</li>
-<li>note the staging repository URL (especially the number at the end of the
URL) you will need this in your vote email</li>
+<li>note the staging repository URL (especially the number at the end of the
URL) you will need this in your vote email.</li>
</ul>
</li>
</ol>
+<h2 id="stage-the-generated-documentation">Stage the generated documentation<a
class="headerlink" href="#stage-the-generated-documentation" title="Permanent
link">¶</a></h2>
+<p>(This only applies to the maven-bundle-plugin so far.)</p>
+<p>Run:</p>
+<div class="codehilite"><pre>$ <span class="n">mvn</span> <span
class="n">site</span><span class="p">:</span><span class="n">site</span> <span
class="n">site</span><span class="p">:</span><span class="n">stage</span> <span
class="n">scm</span><span class="o">-</span><span class="n">publish</span><span
class="p">:</span><span class="n">publish</span><span class="o">-</span><span
class="n">scm</span>
+</pre></div>
+
+
<h2 id="starting-the-vote">Starting the Vote<a class="headerlink"
href="#starting-the-vote" title="Permanent link">¶</a></h2>
<p>Propose a vote on the dev list with the closed issues, the issues left, and
the staging repository - for example:</p>
<div class="codehilite"><pre>To: "Felix Developers List"
<[email protected]>
@@ -336,6 +343,12 @@ Otherwise publish the site by visiting t
<p>For the last two tasks, it's better to give the mirrors some time to
distribute the uploaded artifacts (one day should be fine). This ensures that
once the website (news and download page) is updated, people can actually
download the artifacts.</p>
<h2 id="update-jira">Update JIRA<a class="headerlink" href="#update-jira"
title="Permanent link">¶</a></h2>
<p>Go to <a
href="https://issues.apache.org/jira/secure/project/ViewProject.jspa?pid=12310100";>Admin</a>
section on the FELIX JIRA and mark the Y.Z version as released - create
version Y.Z+1, if that hasn't already been done.</p>
+<h2 id="publish-generated-documentation">Publish Generated Documentation<a
class="headerlink" href="#publish-generated-documentation" title="Permanent
link">¶</a></h2>
+<p>This procedure applies to the maven-bundle-plugin; it may expand to others.
The bundle plugin's maven-site-plugin doc is published to SVN by the
+maven-scm-publish plugin at the location
+https://svn.apache.org/repos/infra/websites/production/felix/content/components/bundle-plugin-archives/bundle-plugin-LATEST.
At release time, you
+rename that from LATEST to the correct version, and then copy it to
https://svn.apache.org/repos/infra/websites/production/felix/content/components/bundle-plugin.</p>
+<p>See <a
href="http://maven.apache.org/developers/website/deploy-component-reference-documentation.html#Publishing_versioned_component_reference_documentation";>some
doc from the Maven project</a>.</p>
<h2 id="create-an-announcement">Create an Announcement<a class="headerlink"
href="#create-an-announcement" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre>To: "Felix Users List"
<[email protected]>
Subject: [ANN] Felix XXX version Y.Z Released
@@ -408,7 +421,7 @@ svn: MKACTIVITY of '/repos/asf/!svn/
<p>This is due to a bug in Subversion on the Mac, as described by Brett Porter
in his
[blog|http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/].
He proposes putting an "svn" script at the head of your path to fix the
issue.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1713666 by bimargulies on Tue, 10 Nov 2015 15:22:37 +0000
+ Rev. 1713908 by bimargulies on Wed, 11 Nov 2015 18:33:50 +0000
</div>
<div class="trademarkFooter">
Apache Felix, Felix, Apache, the Apache feather logo, and the Apache
Felix project
