Author: buildbot
Date: Sun Nov 8 23:09:50 2015
New Revision: 971803
Log:
Staging update by buildbot for juddi
Modified:
websites/staging/juddi/trunk/content/ (props changed)
websites/staging/juddi/trunk/content/committers.html
Propchange: websites/staging/juddi/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Nov 8 23:09:50 2015
@@ -1 +1 @@
-1712197
+1713314
Modified: websites/staging/juddi/trunk/content/committers.html
==============================================================================
--- websites/staging/juddi/trunk/content/committers.html (original)
+++ websites/staging/juddi/trunk/content/committers.html Sun Nov 8 23:09:50
2015
@@ -159,18 +159,29 @@
</div>
<div class="span10" >
- <h2 id="updating-the-juddi-web-site">Updating the jUDDI Web
Site</h2>
+ <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 */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="updating-the-juddi-web-site">Updating the jUDDI Web Site<a
class="headerlink" href="#updating-the-juddi-web-site" title="Permanent
link">¶</a></h2>
<p>The site source is located under our source tree at <a
href="http://svn.apache.org/repos/asf/juddi/cms-site/";>juddi/src/cms-site</a>.
</p>
<p>There are two ways to edit the content for this site.</p>
<ol>
<li>Edit the files in the Subversion repository</li>
<li>Using <a href="https://cms.apache.org/#bookmark";>Apache's CMS
Bookmarklet</a></li>
-<li>Simple <a
href="https://cms.apache.org/redirect?uri=http://juddi.apache.org/";>Click
here</a></li>
+<li>Simply <a
href="https://cms.apache.org/redirect?uri=http://juddi.apache.org/";>Click
here</a></li>
</ol>
<p>Once you're done making edits, commit the changes. Changes can be previewed
on the <a href="http://juddi.staging.apache.org/";>staging site</a>. If you're
satisfied with the results, then publish it to the production site.</p>
<p>Still have questions? Check out <a
href="http://www.apache.org/dev/cms.html";>this</a>, <a
href="http://www.apache.org/dev/cmsref.html";>this</a> and <a
href="http://michelf.ca/projects/php-markdown/extra/";>this</a>.</p>
<p>When updating javadoc or xref sections, it's easier to just use svn and
commit it that way</p>
-<h3 id="notes">Notes</h3>
+<h3 id="notes">Notes<a class="headerlink" href="#notes" title="Permanent
link">¶</a></h3>
<ul>
<li>Each page has a 'Title' header except for the home page.</li>
<li>Content is annotated using <a
href="http://daringfireball.net/projects/markdown/syntax";>Markdown</a></li>
@@ -178,10 +189,10 @@
<li>The home page, uses this <a
href="http://svn.apache.org/repos/asf/juddi/cms-site/trunk/templates/skeletonHome.html";>template</a></li>
<li>When updating the navigation bars (top or left hand side), edit both
templates</li>
</ul>
-<h2 id="release-process">Release Process</h2>
-<h3 id="release-manager">Release Manager</h3>
+<h2 id="release-process">Release Process<a class="headerlink"
href="#release-process" title="Permanent link">¶</a></h2>
+<h3 id="release-manager">Release Manager<a class="headerlink"
href="#release-manager" title="Permanent link">¶</a></h3>
<p>One committer will be elected or hopefully volunteer to assemble the binary
releases and label the source tree.</p>
-<h3 id="digitally-signing-releases">Digitally Signing Releases</h3>
+<h3 id="digitally-signing-releases">Digitally Signing Releases<a
class="headerlink" href="#digitally-signing-releases" title="Permanent
link">¶</a></h3>
<p>Apache policy requires binary releases be digitaly signed. The Apache
process has not been formalized, but a general discussion about creating
digital signatures and signing releases is available at
http://nagoya.apache.org/wiki/apachewiki.cgi?SigningReleases. This covers some
basics about using GnuPG to create key pairs and sign releases. Our goal here
is to discuss jUDDI signing requirements, and provide some useful examples to
release managers, not discuss digital signatures or encryption technology. Our
discussion uses GnuPG, but any compliant software could be used. The examples
below come from the GnuPG manual. This discussion is not a subsitute for
reading that manual.</p>
<p>Creating a key pair is pretty simple using gpg. Simply invoke gpg and take
all the defaults when prompted. You will have to provide a passphrase. Be sure
to remember the passphrase since you'll need it anytime you use the key pair.
The passphrase should itself be sufficiently secure; it shouldn't simply be a
word in a dictionary, should include a mix of digits and alphanumeric
characters, etc.</p>
<div class="codehilite"><pre><span class="n">gpg</span> <span
class="o">--</span><span class="n">gen</span><span class="o">-</span><span
class="n">key</span>
@@ -199,7 +210,7 @@
<p>All jUDDI committers are encouraged to create public/ private key pairs and
place the public half into our 'KEYS' file at the root of our source tree.
jUDDI committers are also encouraged to verify one another's keys and sign
them, to help create a web of trust. Verifying a signature and a binary
guarantees (in any real sense) the binary was assembled by the person that
signed it. However, it does not prove the person signing it can be trusted. A
web of trust can be created by signing one another's keys. This allows users
and developers to 'trust' the person who created the document-signature pair to
provide a secure, safe binary.</p>
-<h3 id="release-procedure">Release Procedure</h3>
+<h3 id="release-procedure">Release Procedure<a class="headerlink"
href="#release-procedure" title="Permanent link">¶</a></h3>
<ol>
<li>Ensure the build works (mvn clean install -Pdist)</li>
<li>Grab the current version's release notes using JIRA. Goto JIRA, Versions,
pick the version, then Release notes. Replace the release notes html file
within the source with the contents from JIRA.</li>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
