You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bu...@apache.org on 2013/05/29 16:05:51 UTC
svn commit: r863631 - in /websites/staging/sling/trunk/content: ./
documentation/development/release-management.html
Author: buildbot
Date: Wed May 29 14:05:51 2013
New Revision: 863631
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/development/release-management.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed May 29 14:05:51 2013
@@ -1 +1 @@
-1487487
+1487493
Modified: websites/staging/sling/trunk/content/documentation/development/release-management.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/development/release-management.html (original)
+++ websites/staging/sling/trunk/content/documentation/development/release-management.html Wed May 29 14:05:51 2013
@@ -318,23 +318,28 @@ Enjoy!
<p>Considering that you are using a *nix system with a working OpenSSH, GnuPG, and bash you can create and add your own key with the following command:</p>
<ol>
<li>
-<p><em>Create a public/private pair key</em>:</p>
-<p>$ gpg --gen-key</p>
-</li>
-</ol>
+<p>Create a public/private pair key:</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">gpg</span> <span class="o">--</span><span class="n">gen</span><span class="o">-</span><span class="n">key</span>
+</pre></div>
+
+
<p>When gpg asks for e-mail linked the key you <em>MUST USE</em> the <committer>@apache.org one
-When gpg asks for comment linked the key you <em>SHOULD USE</em> "CODE SIGNING KEY"
-1. <em>Add the key to</em> <a href="http://www.apache.org/dist/sling/KEYS">http://www.apache.org/dist/sling/KEYS</a> type the following command replacing the word e-mail with your Apache's one (<committer>@apache.org).</p>
+When gpg asks for comment linked the key you <em>SHOULD USE</em> "CODE SIGNING KEY"</p>
+</li>
+<li>
+<p>Add the key to <a href="http://www.apache.org/dist/sling/KEYS">http://www.apache.org/dist/sling/KEYS</a> type the following command replacing the word e-mail with your Apache's one (<committer>@apache.org).</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="n">e</span><span class="o">-</span><span class="n">mail</span> <span class="o">&&</span> <span class="n">gpg</span> <span class="o">--</span><span class="n">export</span> <span class="o">--</span><span class="n">armor</span> <span class="n">e</span><span class="o">-</span><span class="n">mail</span><span class="p">)</span> <span class="o">></span> <span class="n">toadd</span><span class="o">.</span><span class="n">key</span>
<span class="nv">$</span> <span class="nv">scp</span> <span class="n">toadd</span><span class="o">.</span><span class="n">key</span> <span class="n">people</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org:</span>
<span class="nv">$</span> <span class="nv">ssh</span> <span class="n">people</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span> <span class="s">"cat toadd.key >> /x1/www/www.apache.org/dist/sling/KEYS"</span>
</pre></div>
-<ol>
-<li>You are <em>DONE</em>, but to see the changes on <a href="http://www.apache.org/dist/sling/KEYS">http://www.apache.org/dist/sling/KEYS</a> you must wait 2 hours</li>
-</ol>
+</li>
+<li>
+<p>You are <em>DONE</em>, but to see the changes on <a href="http://www.apache.org/dist/sling/KEYS">http://www.apache.org/dist/sling/KEYS</a> you must wait 2 hours</p>
<p>You also have to add your public key either on pool.sks-keyservers.net or pgp.mit.edu (for the statging repository).</p>
+</li>
+</ol>
<h2 id="appendix-b-preparing-releases-on-mac-os-x">Appendix B: preparing releases on Mac OS X</h2>
<p>When running the <code>mvn release:prepare</code> command on Mac OS X, you might see the following error:</p>
<div class="codehilite"><pre><span class="p">[</span><span class="n">INFO</span><span class="p">]</span> <span class="n">Working</span> <span class="n">directory:</span> <span class="sr">/homedir/</span><span class="n">dev</span><span class="sr">/sling/</span><span class="n">dependencymanager</span>
@@ -350,9 +355,9 @@ When gpg asks for comment linked the key
</pre></div>
-<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>
+<p>This is due to a bug in Subversion on the Mac, as described by Brett Porter in his <a href="http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/">blog</a>. He proposes putting an "svn" script at the head of your path to fix the issue.</p>
<h2 id="appendix-c-deploy-bundles-on-the-sling-obr">Appendix C: Deploy bundles on the Sling OBR</h2>
-<p>We are mainting an OSGi Bundle Repository providing all release of the Sling Bundles. This repository is maintained as part of the Apache Sling site and is available at [http://sling.apache.org/obr/sling.xml]. The source for this page is maintained in the SVN repository below the <em>site</em>, that is at [http://svn.apache.org/repos/asf/sling/site/]. To update the Sling OBR repository you must be an Apache Sling Committer since this requires SVN write access.</p>
+<p>We are mainting an OSGi Bundle Repository providing all release of the Sling Bundles. This repository is maintained as part of the Apache Sling site and is available at <a href="http://sling.apache.org/obr/sling.xml">http://sling.apache.org/obr/sling.xml</a>. The source for this page is maintained in the SVN repository below the <em>site</em>, that is at <a href="http://svn.apache.org/repos/asf/sling/site/">http://svn.apache.org/repos/asf/sling/site/</a>. To update the Sling OBR repository you must be an Apache Sling Committer since this requires SVN write access.</p>
<p>To update the OBR you may use the Apache Felix Maven Bundle Plugin which prepares the bundle descriptor to be added to the OBR file. Follow these steps to update the OBR:</p>
<ol>
<li>
@@ -402,17 +407,17 @@ When gpg asks for comment linked the key
</li>
<li>
-<p>Update the Site on [people.apache.org]{people.apache.org}</p>
-</li>
-</ol>
-<p>After committing the changes, you have to update the site source, which is getting mirrored to the web servers on [people.apache.org]{people.apache.org}</p>
+<p>Update the Site on <a href="people.apache.org">people.apache.org</a></p>
+<p>After committing the changes, you have to update the site source, which is getting mirrored to the web servers on <a href="people.apache.org">people.apache.org</a></p>
<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">ssh</span> <span class="n">people</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span> <span class="n">svn</span> <span class="n">update</span> <span class="sr">/x1/</span><span class="n">www</span><span class="sr">/sling.apache.org/o</span><span class="n">br</span><span class="o">/</span><span class="n">sling</span><span class="o">.</span><span class="n">xml</span>
</pre></div>
<p>After updating the site source it will generally take an hour or two until the changes are visible on the web.</p>
+</li>
+</ol>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1487487 by dklco on Wed, 29 May 2013 13:53:44 +0000
+ Rev. 1487493 by dklco on Wed, 29 May 2013 14:05:44 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project