This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git


The following commit(s) were added to refs/heads/asf-staging by this push:
     new ce6daf6  Automatic Site Publish by Buildbot
ce6daf6 is described below

commit ce6daf608ecb8600a6ec1be3ae76d7c8859904cd
Author: buildbot <us...@infra.apache.org>
AuthorDate: Mon Oct 19 18:19:48 2020 +0000

    Automatic Site Publish by Buildbot
---
 output/contributor/versioning.html | 34 ++++++++++++++++++++--------------
 output/feed.xml                    |  4 ++--
 output/index.html                  |  2 +-
 3 files changed, 23 insertions(+), 17 deletions(-)

diff --git a/output/contributor/versioning.html 
b/output/contributor/versioning.html
index 082ab66..7b3d766 100644
--- a/output/contributor/versioning.html
+++ b/output/contributor/versioning.html
@@ -144,31 +144,37 @@
 
 <p>The Apache Accumulo PMC has adopted a Long Term Maintenance (LTM) release 
strategy.</p>
 
-<p>This strategy entails an intent to:</p>
+<h3 id="ltm-versions">LTM Versions:</h3>
 
 <ol>
   <li>Periodically release a new LTM <code class="language-plaintext 
highlighter-rouge">major.minor.0</code> version (approximately every 2 
years),</li>
   <li>Maintain the LTM releases with <code class="language-plaintext 
highlighter-rouge">major.minor.(patch++)</code> releases until 1 year after the 
next LTM,</li>
-  <li>Release intermediate non-LTM <code class="language-plaintext 
highlighter-rouge">major.minor.0</code> versions that are not expected to 
receive patch/bugfix releases,</li>
-  <li>Roll patches/bugfixes targeting non-LTM versions into the next <code 
class="language-plaintext highlighter-rouge">major.minor.0</code> release, 
and</li>
-  <li>Support upgrades from both the immediately preceding LTM and non-LTM 
versions.</li>
+  <li>Support upgrades from both the immediately preceding LTM and non-LTM 
versions</li>
 </ol>
 
 <p>This strategy implies that no more than one or two LTM releases will be
-actively maintained at any given time, with a one year overlap.</p>
+actively maintained at any given time, with one year of overlap.</p>
+
+<h3 id="non-ltm-versions">Non-LTM versions:</h3>
+
+<ol>
+  <li>Release intermediate non-LTM <code class="language-plaintext 
highlighter-rouge">major.minor.0</code> versions that are not expected to 
receive patch/bugfix releases,</li>
+  <li>Roll patches/bugfixes targeting non-LTM versions into the next <code 
class="language-plaintext highlighter-rouge">major.minor.0</code> release</li>
+</ol>
 
-<p>The motivation for this is to streamline the work of maintaining multiple
-versions of Accumulo while not inhibiting development on newer versions, to
-provide greater confidence for risk-averse users to upgrade to versions that
-are expected to be stable and receive updates (with a one year window to do
-so), and help reduce the amount of work done by limiting upgrade paths.</p>
+<h3 id="goals-of-the-ltm-strategy">Goals of the LTM strategy:</h3>
+<ul>
+  <li>Streamline maintaining multiple versions of Accumulo</li>
+  <li>Encourage development on newer versions</li>
+  <li>Provide greater confidence for users to upgrade and receive updates 
(within one year)</li>
+  <li>Help reduce the amount of work done by limiting upgrade paths</li>
+</ul>
 
 <p>Note: the above strategy is a declaration of <strong>intent</strong> only. 
We use the term
 “Long Term Maintenance” rather than the more familiar “Long Term Support” or
-“Long Term Stable” terms to avoid possible confusion that may arise over
-implication of warrantees from the use of the words “support” or “stable”. See
-the project LICENSE for a full disclaimer of warranties. If you have questions,
-about this, please <a href="/contact-us">contact</a> us.</p>
+“Long Term Stable” terms to avoid any implication of warranties
+from the use of the words “support” or “stable”. See the project LICENSE for a 
full
+disclaimer of warranties. If you have questions, about this, please <a 
href="/contact-us">contact</a> us.</p>
 
 <h2 id="semver-200">SemVer 2.0.0</h2>
 
diff --git a/output/feed.xml b/output/feed.xml
index b4e32b1..1fe5ec0 100644
--- a/output/feed.xml
+++ b/output/feed.xml
@@ -6,8 +6,8 @@
 </description>
     <link>https://accumulo.apache.org/</link>
     <atom:link href="https://accumulo.apache.org/feed.xml"; rel="self" 
type="application/rss+xml"/>
-    <pubDate>Mon, 19 Oct 2020 15:27:20 +0000</pubDate>
-    <lastBuildDate>Mon, 19 Oct 2020 15:27:20 +0000</lastBuildDate>
+    <pubDate>Mon, 19 Oct 2020 18:19:43 +0000</pubDate>
+    <lastBuildDate>Mon, 19 Oct 2020 18:19:43 +0000</lastBuildDate>
     <generator>Jekyll v4.1.1</generator>
     
     
diff --git a/output/index.html b/output/index.html
index 5a97e30..5e09149 100644
--- a/output/index.html
+++ b/output/index.html
@@ -167,7 +167,7 @@
       </div>
       <div class="col-md-6">
         <h4>Stable</h4>
-        <p>Accumulo has a stable <a href="/latest/apidocs">client API</a> that 
follows <a href="https://semver.org";>semantic versioning</a>. Each Accumulo 
release goes through <a 
href="/docs/2.x/getting-started/features#testing">extensive testing</a>.</p>
+        <p>Accumulo has a stable <a href="/latest/apidocs">client API</a> that 
follows <a href="/contributor/versioning">LTM releases and semantic 
versioning</a>. Each Accumulo release goes through <a 
href="/docs/2.x/getting-started/features#testing">extensive testing</a>.</p>
       </div>
     </div>
   </div>

Reply via email to