[
https://issues.apache.org/jira/browse/LUCENE-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13970727#comment-13970727
]
Uwe Schindler edited comment on LUCENE-5607 at 4/16/14 12:34 PM:
-----------------------------------------------------------------
{quote}
With the JavaBugs page, I am not saying it is out of date. I am saying it is
hard to understand at the glance whether it applies to whatever I am running.
So, when we move to Java 7 and recommend the latest u60+, how much of that page
will be relevant to those users? Can we put the issues that are still
open/affect even u60+ on the top and move the rest into the noticeably
different section?
In addition, we have lots of users, still using Lucene 2.9.x / Solr 1.4.x and
Lucene/Solr 3.6.x. For those people we should keep the complete list of bugs,
especially to help them if they hit one of these bugs to help them to
workaround.
But perhaps it is a different issue and different discussion.
{quote}
Feel free to update this page in the Wiki! I try to update them whenever we
find new bugs and issues. Unfortunately, it is not always easy to check that
every bug is still valid, so it is better to keep them in the list.
Sorting the page by version numbers could be done, yes (like we do for JDK
vendors).
was (Author: thetaphi):
{quote}
With the JavaBugs page, I am not saying it is out of date. I am saying it is
hard to understand at the glance whether it applies to whatever I am running.
So, when we move to Java 7 and recommend the latest u60+, how much of that page
will be relevant to those users? Can we put the issues that are still
open/affect even u60+ on the top and move the rest into the noticeably
different section?
But perhaps it is a different issue and different discussion.
{quote}
Feel free to update this page in the Wiki! I try to update them whenever we
find new bugs and issues. Unfortunately, it is not always easy to check that
every bug is still valid, so it is better to keep them in the list.
Sorting the page by version numbers could be done, yes (like we do for JDK
vendors).
> Update SYSTEM_REQUIREMENTS.txt and update Java-7-known-to-work version
> numbers before release of Lucene/Solr 4.8
> ----------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-5607
> URL: https://issues.apache.org/jira/browse/LUCENE-5607
> Project: Lucene - Core
> Issue Type: Task
> Components: general/javadocs
> Reporter: Alexandre Rafalovitch
> Assignee: Uwe Schindler
> Priority: Blocker
> Labels: documentation
> Fix For: 4.8
>
>
> Since Solr 4.8 will require Java 7 as a minimum, the description in the
> SYSTEM_REQUIREMENTS.txt need to be updated too.
> Or maybe it should be merged into release notes. All it will probably have is
> use Java version after u56 (or whatever) and here is an obscure URL to known
> bugs (still valid for Java 7?).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
