OK, it looks like Java 7 starting with Solr 4.8 is going to happen. May I suggest we announce this sooner rather than later? Perhaps starting with an announcement on the user's list Real Soon Now? Like before we break people's builds that rely on Java 1.6 with a checkin to 4x?
There will be organizations for which this is a total deal-killer for 4.8. I'm _not_ advocating that we stay on 1.6 because of that, rather that we give them a chance to start planning/adjusting soon. Additionally, there's a fair likelihood that some of the organizations stuck on 1.6 have a long vetting process before 1.7 would be used, so the more time they have the better if they consider Solr mission-critical. On Tue, Mar 11, 2014 at 12:31 PM, Mike Murphy <[email protected]> wrote: > On Tue, Mar 11, 2014 at 6:11 AM, Grant Ingersoll <[email protected]> wrote: >> >> On Mar 8, 2014, at 11:17 AM, Uwe Schindler <[email protected]> wrote: >> >> [.] Move Lucene/Solr 4.8 (means branch_4x) to Java 7 and backport all Java >> 7-related issues (FileChannel improvements, diamond operator,...). >> >> >> -0 -- Seems a little odd that we would force an upgrade on a minor version, >> which is not usually seen as best practice in development. > > I agree. I also do not see it making a difference to potential developers. > What are the benefits to the project? A developer will not make their > decision to get involved in Lucene/Solr based on branch4x being Java 6 > vs Java 7. > If causes some users to not upgrade, that's also a bad thing for the project. > > -Mike > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
