[accumulo-website] branch asf-staging updated: Automatic Site Publish by Buildbot

2020-10-19 Thread git-site-role
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 b813733  Automatic Site Publish by Buildbot
b813733 is described below

commit b81373326470d3f823c518c4db51ee6b38ab7edc
Author: buildbot 
AuthorDate: Mon Oct 19 15:27:26 2020 +

Automatic Site Publish by Buildbot
---
 output/feed.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/output/feed.xml b/output/feed.xml
index f97054e..b4e32b1 100644
--- a/output/feed.xml
+++ b/output/feed.xml
@@ -6,8 +6,8 @@
 
 https://accumulo.apache.org/
 https://accumulo.apache.org/feed.xml"; rel="self" 
type="application/rss+xml"/>
-Fri, 09 Oct 2020 20:31:27 +
-Fri, 09 Oct 2020 20:31:27 +
+Mon, 19 Oct 2020 15:27:20 +
+Mon, 19 Oct 2020 15:27:20 +
 Jekyll v4.1.1
 
 



[accumulo-website] branch main updated: Update Gemfile with new versions (#245)

2020-10-19 Thread mmiller
This is an automated email from the ASF dual-hosted git repository.

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


The following commit(s) were added to refs/heads/main by this push:
 new ac4489f  Update Gemfile with new versions (#245)
ac4489f is described below

commit ac4489f868bac3d5185b8725fdc8a71964f5d9dc
Author: Mike Miller 
AuthorDate: Mon Oct 19 11:26:47 2020 -0400

Update Gemfile with new versions (#245)
---
 Gemfile.lock | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Gemfile.lock b/Gemfile.lock
index 5826365..177f749 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -5,7 +5,7 @@ GEM
   public_suffix (>= 2.0.2, < 5.0)
 colorator (1.1.0)
 concurrent-ruby (1.1.7)
-em-websocket (0.5.1)
+em-websocket (0.5.2)
   eventmachine (>= 0.12.9)
   http_parser.rb (~> 0.6.0)
 eventmachine (1.2.7)
@@ -53,7 +53,7 @@ GEM
   ffi (~> 1.0)
 ref (2.0.0)
 rexml (3.2.4)
-rouge (3.22.0)
+rouge (3.24.0)
 safe_yaml (1.0.5)
 sassc (2.4.0)
   ffi (~> 1.9)



Buildbot success in on jekyll_websites

2020-10-19 Thread buildbot
The Buildbot has detected a passing build on builder jekyll_websites while 
building accumulo.
Full details are available at:
https://ci2.apache.org/#builders/7/builds/225

Buildbot URL: https://ci2.apache.org/

Worker for this Build: bb_slave10_ubuntu

Build Reason: Triggered jekyll auto-build via .asf.yaml by mmiller
Blamelist: asfinfra, commits@accumulo.apache.org

Build succeeded!

Sincerely,
 -The Buildbot



[accumulo-website] branch main updated: Improve the LTM wording (#246)

2020-10-19 Thread mmiller
This is an automated email from the ASF dual-hosted git repository.

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


The following commit(s) were added to refs/heads/main by this push:
 new e98b242  Improve the LTM wording (#246)
e98b242 is described below

commit e98b24273b638fbd673ab7a23204b13c70238395
Author: Mike Miller 
AuthorDate: Mon Oct 19 14:19:19 2020 -0400

Improve the LTM wording (#246)

* Update contributor/versioning.md
* Simplify some of the wording in the LTM description
* Minor spelling corrections
* Make ### sections and link to versioning on front page


Co-authored-by: Christopher Tubbs 
---
 contributor/versioning.md | 30 --
 index.html|  2 +-
 2 files changed, 17 insertions(+), 15 deletions(-)

diff --git a/contributor/versioning.md b/contributor/versioning.md
index 1c60f18..8fad01f 100644
--- a/contributor/versioning.md
+++ b/contributor/versioning.md
@@ -8,29 +8,31 @@ redirect_from: /versioning
 
 The Apache Accumulo PMC has adopted a Long Term Maintenance (LTM) release 
strategy.
 
-This strategy entails an intent to:
+### LTM Versions:
 
 1. Periodically release a new LTM `major.minor.0` version (approximately every 
2 years),
 2. Maintain the LTM releases with `major.minor.(patch++)` releases until 1 
year after the next LTM,
-3. Release intermediate non-LTM `major.minor.0` versions that are not expected 
to receive patch/bugfix releases,
-4. Roll patches/bugfixes targeting non-LTM versions into the next 
`major.minor.0` release, and
-5. Support upgrades from both the immediately preceding LTM and non-LTM 
versions.
+3. Support upgrades from both the immediately preceding LTM and non-LTM 
versions
 
 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.
+actively maintained at any given time, with one year of overlap.
 
-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.
+### Non-LTM versions:
+
+1. Release intermediate non-LTM `major.minor.0` versions that are not expected 
to receive patch/bugfix releases,
+2. Roll patches/bugfixes targeting non-LTM versions into the next 
`major.minor.0` release
+
+### Goals of the LTM strategy:
+- Streamline maintaining multiple versions of Accumulo
+- Encourage development on newer versions
+- Provide greater confidence for users to upgrade and receive updates (within 
one year)
+- Help reduce the amount of work done by limiting upgrade paths
 
 Note: the above strategy is a declaration of **intent** 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 [contact] us.
+"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 [contact] 
us.
 
 ## SemVer 2.0.0
 {: semver }
diff --git a/index.html b/index.html
index 0675444..73ee180 100644
--- a/index.html
+++ b/index.html
@@ -31,7 +31,7 @@ skiph1fortitle: true
   
   
 Stable
-Accumulo has a stable client API that 
follows https://semver.org";>semantic versioning. Each Accumulo 
release goes through extensive testing.
+Accumulo has a stable client API that 
follows LTM releases and 
semantic versioning. Each Accumulo release goes through extensive 
testing.
   
 
   



[accumulo-website] branch asf-staging updated: Automatic Site Publish by Buildbot

2020-10-19 Thread git-site-role
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 
AuthorDate: Mon Oct 19 18:19:48 2020 +

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 @@
 
 The Apache Accumulo PMC has adopted a Long Term Maintenance (LTM) release 
strategy.
 
-This strategy entails an intent to:
+LTM Versions:
 
 
   Periodically release a new LTM major.minor.0 version (approximately every 2 
years),
   Maintain the LTM releases with major.minor.(patch++) releases until 1 year after the 
next LTM,
-  Release intermediate non-LTM major.minor.0 versions that are not expected to 
receive patch/bugfix releases,
-  Roll patches/bugfixes targeting non-LTM versions into the next major.minor.0 release, 
and
-  Support upgrades from both the immediately preceding LTM and non-LTM 
versions.
+  Support upgrades from both the immediately preceding LTM and non-LTM 
versions
 
 
 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.
+actively maintained at any given time, with one year of overlap.
+
+Non-LTM versions:
+
+
+  Release intermediate non-LTM major.minor.0 versions that are not expected to 
receive patch/bugfix releases,
+  Roll patches/bugfixes targeting non-LTM versions into the next major.minor.0 release
+
 
-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.
+Goals of the LTM strategy:
+
+  Streamline maintaining multiple versions of Accumulo
+  Encourage development on newer versions
+  Provide greater confidence for users to upgrade and receive updates 
(within one year)
+  Help reduce the amount of work done by limiting upgrade paths
+
 
 Note: the above strategy is a declaration of intent 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 contact us.
+“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 contact us.
 
 SemVer 2.0.0
 
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 @@
 
 https://accumulo.apache.org/
 https://accumulo.apache.org/feed.xml"; rel="self" 
type="application/rss+xml"/>
-Mon, 19 Oct 2020 15:27:20 +
-Mon, 19 Oct 2020 15:27:20 +
+Mon, 19 Oct 2020 18:19:43 +
+Mon, 19 Oct 2020 18:19:43 +
 Jekyll v4.1.1
 
 
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 @@
   
   
 Stable
-Accumulo has a stable client API that 
follows https://semver.org";>semantic versioning. Each Accumulo 
release goes through extensive testing.
+Accumulo has a stable client API that 
follows LTM releases and semantic 
versioning. Each Accumulo release goes through extensive testing.
   
 
   



Buildbot success in on jekyll_websites

2020-10-19 Thread buildbot
The Buildbot has detected a passing build on builder jekyll_websites while 
building accumulo.
Full details are available at:
https://ci2.apache.org/#builders/7/builds/227

Buildbot URL: https://ci2.apache.org/

Worker for this Build: bb_slave10_ubuntu

Build Reason: Triggered jekyll auto-build via .asf.yaml by mmiller
Blamelist: asfinfra, commits@accumulo.apache.org

Build succeeded!

Sincerely,
 -The Buildbot



[accumulo-website] branch asf-site updated (3527c82 -> ce6daf6)

2020-10-19 Thread mmiller
This is an automated email from the ASF dual-hosted git repository.

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


from 3527c82  Automatic Site Publish by Buildbot
 add dab9270  Automatic Site Publish by Buildbot
 add b813733  Automatic Site Publish by Buildbot
 add ce6daf6  Automatic Site Publish by Buildbot

No new revisions were added by this update.

Summary of changes:
 output/contributor/versioning.html | 34 --
 output/feed.xml|  4 ++--
 output/index.html  |  2 +-
 output/people/index.html   |  5 +
 4 files changed, 28 insertions(+), 17 deletions(-)