Thanks Shawn for the support! From: Shawn Heisey [mailto:s...@elyograg.org] > Sent: Saturday, March 08, 2014 8:23 PM > To: dev@lucene.apache.org > Subject: Re: [VOTE] Move to Java 7 in Lucene/Solr 4.8, use Java 8 in trunk > (once officially released) > > On 3/8/2014 9:17 AM, Uwe Schindler wrote: > > [.] Move Lucene/Solr 4.8 (means branch_4x) to Java 7 and backport all Java > 7-related issues (FileChannel improvements, diamond operator,...). > > +1 > > We might want to wait until 4.9, so we can use the 4.8 release to announce > that the change is coming. My vote is still +1 even if we move before the 4.8 > release.
I don't think it would help those people, if they would get the information one release before in the release notes. We should upgrade for 4.8, only announce it on the user mailing lists and on the news section of the website once this vote succeeded. > I know that this is going to cause heartburn for a lot of people, but > honestly if > they don't already know that Java 6 has had no public support for over a year, > they haven't been paying attention. I no longer use Java 6 except for > smoketester runs at release time. > > I doubt that our general target audience includes the subset of people that > are willing to pay Oracle a lot of money for support. My small experience > with non-Oracle Java 6 implementations indicates that as a group, they do > not work well with Lucene/Solr. > > As already noted in other discussions, there have been some events where > Java 7 code made it into 4.x before being caught by Jenkins or the > smoketester. Although these are currently a trickle, I believe that if we > continue to have Java 6 as a requirement, it will quickly turn into a flood. Example? I only know of this, when we had that my last minute commits in one of our RCs, but this was found by the release manager. This cannot happen, because it is mandatory that the release artifacts are built with Java 6 - smoketester checks this from the manifest of the JARs! > Do we think there is much chance of code written for (and compiled with) > Java 6 to fail to run on Java 8? If so, that's another reason to abandon it. No. We test the stuff with Java 8 since one year. Works perfectly fine! We found bugs in the JDK, but not in our code - except maybe bugs in solr caused by the new and unpredictable string-hashmap order. Uwe --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
