Thanks. I included your suggestions. The whole paragraph now reads: Apache Solr is under active development with frequent feature releases on the current major version (e.g. 6.x). 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. 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 only included in the next major version (e.g. 7.0). For more about versions and upgrading Solr, see the Reference Guide chapter “Upgrading Solr” <https://cwiki.apache.org/confluence/display/solr/Upgrading+Solr>.
I don’t like putting version numbers into the website, since they WILL be out of date at some point. But it is hard to explain three generations without giving examples, suggestions for how to avoid it? -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 12. jan. 2017 kl. 19.22 skrev Shawn Heisey <apa...@elyograg.org>: > > On 1/12/2017 12:35 AM, Jan Høydahl wrote: >> Good points, see proposed rephrasing >> in http://lucene.staging.apache.org/solr/community.html >> >> I think people understand that in the context of an Apache open source >> project, the word “Support” means all kind of question answering, >> bug-fixes etc that the community provides. But it could perhaps >> bestated in a better way in that paragraph? > > This is how I would phrase it (starting with what's on the staging site): > > "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." > > I think it's a good idea to start a new paragraph after that statement. > I would also rephrase a later sentence, mostly because of the incorrect > word (braking) it currently contains: > > "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 (currently 7.0)." > > Thanks, > Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org >
