svn commit: r1004768 - in /websites/staging/lucene/trunk/content: ./ solr/community.html

[bu...@apache.org]

Author: buildbot
Date: Thu Jan 12 22:24:07 2017
New Revision: 1004768

Log:
Staging update by buildbot for lucene

Modified:
    websites/staging/lucene/trunk/content/   (props changed)
    websites/staging/lucene/trunk/content/solr/community.html

Propchange: websites/staging/lucene/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jan 12 22:24:07 2017
@@ -1 +1 @@
-1778478
+1778482

Modified: websites/staging/lucene/trunk/content/solr/community.html
==============================================================================
--- websites/staging/lucene/trunk/content/solr/community.html (original)
+++ websites/staging/lucene/trunk/content/solr/community.html Thu Jan 12 22:24:07 2017
@@ -226,11 +226,9 @@ here. There are also a number of externa
 The previous major version (e.g. 5.5) may still receive security- and bug fixes as point releases, thus taking the role 
 of the LTS (Long Term Support) version.
 Older versions are considered EOL (End Of Life) and will not be further
-updated. Because there can be no further changes, it may also be
-difficult to obtain community support for the older versions.
+updated. For this reason it may also be difficult to obtain community support for EOL versions.
 Large changes or changes that break compatibility with existing
-functionality are normally made only in the "master" branch, which will
-be released as the the next major version (e.g. 7.0).
+functionality are normally only included in the next major version (e.g. 7.0).
 For more about versions and upgrading Solr, see the 
 <a href="https://cwiki.apache.org/confluence/display/solr/Upgrading+Solr">Reference Guide chapter “Upgrading Solr”</a>.</p>
 <h2 id="mailing-lists-irc">Mailing Lists &amp; IRC<a class="headerlink" href="#mailing-lists-irc" title="Permanent link">&para;</a></h2>