Author: buildbot
Date: Sun Dec 14 19:05:36 2014
New Revision: 932726

Log:
Staging update by buildbot for accumulo

Modified:
    websites/staging/accumulo/trunk/content/   (props changed)
    websites/staging/accumulo/trunk/content/versioning.html

Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Dec 14 19:05:36 2014
@@ -1 +1 @@
-1645493
+1645494

Modified: websites/staging/accumulo/trunk/content/versioning.html
==============================================================================
--- websites/staging/accumulo/trunk/content/versioning.html (original)
+++ websites/staging/accumulo/trunk/content/versioning.html Sun Dec 14 19:05:36 
2014
@@ -192,10 +192,11 @@ Latest 1.5 release: <strong>1.5.2</stron
 
     <h1 class="title">Apache Accumulo Versioning</h1>
 
-    <p>The PMC of Apache Accumulo closed a vote on 2014/12/12 which adopted <a 
href="http://semver.org/spec/v2.0.0.html";>Semantic Versioning 2.0.0</a> as
-the reference document on the meaning and requirements of subsequent releases 
of Apache Accumulo. The definition
-of the public API is unchanged over previous releases and can be found in 
section 9 of the <a 
href="https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob;f=README;hb=refs/heads/master";>README</a>.</p>
-<p>The semantic versioning specification is included here:</p>
+    <p>The Apache Accumulo PMC closed a vote on 2014/12/12 which adopted <a 
href="http://semver.org/spec/v2.0.0.html";>Semantic Versioning 2.0.0</a> as
+the reference document on the meaning and requirements of subsequent releases 
of Apache Accumulo. Semantic
+versioning requires a definition of a public API: this definition is unchanged 
over previous releases and
+can be found in section 9 of the <a 
href="https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob;f=README;hb=refs/heads/master";>README</a>.</p>
+<h2 id="versioning">Versioning</h2>
 <p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
 in this document are to be interpreted as described in RFC 2119.</p>
 <ol>


Reply via email to